HomeOctober 2026 patch cycleFortiOS 7.4 and 7.6: the GUI daemon that eats the firewall (bug 1227167)
Call: Known issueCategory: EnterpriseCategory: Homelabfrom 2026-10
Issue from: FortiOS CVE-2025-61624: an April fix, an October KEV entry, and an implant called PEERSTITCH
FortiOS 7.4 and 7.6: the GUI daemon that eats the firewall (bug 1227167)
Part of October 2026 patch cycle
- Vendor
- Fortinet
- Products
- FortiOS 7.4 and FortiOS 7.6
- Published
- Status
- Open
Call: Known issue. The node daemon, which runs the FortiOS web GUI, leaks memory until the FortiGate drops into conserve mode. Fortinet tracks it as bug 1227167. It sits in the builds that fix CVE-2025-61624, which is being exploited in the wild, so going backwards is not an option. Go forward to 7.4.13, and turn on the auto-restart workaround wherever you can’t upgrade yet.
Update, Oct 26: 7.6.8 breaks admin SAML SSO. Fortinet confirms that after upgrading to 7.6.8, administrator SSO fails with “Single Sign-On Failed”. It’s in the 7.6.8 release notes as known issue 1338764, and in a Fortinet support article.
- Affected: admin FortiCloud SSO, admin SAML with a third-party IdP such as Entra ID, and Security Fabric SSO to downstream FortiGates.
- Not affected: VPN user SSO, local admins, RADIUS, LDAP and TACACS+ admins, and FortiOS 7.2.14, 7.4.13, 7.6.7 and 8.0.2.
- Fix: Fortinet schedules it for 7.6.9 and gives no date.
- Workaround: use another admin authentication method. If you have none, you’ll need console access or FortiManager to recover.
- How to confirm it: log in as a local admin and look for a “FORTISM Violation” in
diagnose debug crashlog read. - What to do on 7.6: staying on 7.6.7 isn’t an answer. Fortinet’s Oct 22 hardening release fixes critical and high-severity bugs in everything below 7.6.8. Before upgrading, create a local or RADIUS/LDAP/TACACS+ admin and test it, with trusted hosts and MFA, then upgrade.
Two more 7.6.8 known issues are worth a look before you upgrade:
- Hardware-specific: the 1800F/1801F drops traffic on SFP ports (1353422), and interfaces stay down on the 370xF and 480xF (1353040).
- All the hardening builds, including 7.4.13: with deep inspection on, websites on non-standard HTTPS ports such as 8443 return
ERR_EMPTY_RESPONSE(1353958).
Affected: Fortinet lists 1227167 under Known Issues for FortiOS 7.4.9, 7.4.10, 7.4.11, 7.4.12 and 7.6.6. Users report the same leak on 7.6.7, although the 7.6.7 release notes don’t list it. Fortinet’s own article scopes it to “FortiOS v7.4.x and v7.6.x”.
Fixed in: 7.4.13 (build 2933, Oct 22) and 8.0.1 both list 1227167 as resolved. On 7.6, Fortinet’s article says the fix is expected in 7.6.8 (build 3744, Oct 22). The 7.6.8 resolved list doesn’t name 1227167, but it does include two V8 JavaScript engine memory fixes, 1212624 and 1225806, and 1227167 is no longer among its known issues. Until 7.6.8 is shown to hold, treat it as probably fixed, not confirmed.
What breaks:
nodememory climbs over days or weeks. One 80F on 7.4.11 went from 85 MB to 230 MB in three days, and Fortinet’s example shows 603 MB.- The unit crosses the 88% red threshold and enters conserve mode.
- Users report the GUI going unreachable. Separately, a 50G HA pair on 7.6.7 kept dropping into conserve mode and losing routing until it failed over or rebooted, though that thread never pinned it on a specific daemon.
Who’s hit: Mostly small-memory boxes (40F, 60F, 80F, 50G) on the builds above, since 2 GB and 4 GB of RAM leaves little headroom. An older Fortinet article names Security Fabric and FortiManager polling as things that make node work harder.
Watch the CVE math: CVE-2025-61624 is fixed in 7.4.10+ and 7.6.5+. That means 7.4.10 through 7.4.12 and 7.6.6 are patched for the exploited bug and leak anyway. Rolling back to 7.4.9 trades the leak for an exploited vulnerability, and 7.4.9 leaks too. Only 7.4.13 is confirmed clean on both counts.
Workaround:
- Check whether you’re hit. Run
diagnose sys top-mem 5andget system performance status | grep Mema few times over several hours. Ifnodekeeps growing, you’re hit. - Turn on Fortinet’s workaround, which restarts
nodewhen it crosses a memory threshold:
config system global
set web-svc-auto-restart enable
end
- To clear it by hand, run
diagnose nodejs process restart. - Before upgrading from 7.4.11 or 7.6.6, turn
web-svc-auto-restartoff and turn it back on afterwards. Leaving it on during the upgrade to 7.4.12 or 7.6.7 wipes someconfig system globalsettings (hostname, timezone, admin-scp, VDOM mode). That’s bug 1277454, fixed in 7.4.13 and 7.6.8.
Sources: FortiOS 7.6.8 known issues (opens in a new tab), Fortinet: admin SSO fails after 7.6.8 (opens in a new tab), Fortinet hardening release (opens in a new tab), FortiOS 7.4.12 known issues (opens in a new tab), 7.4.13 resolved issues (opens in a new tab), 7.6.6 known issues (opens in a new tab), 7.6.8 resolved issues (opens in a new tab), Fortinet community: node conserve mode in 7.4.x/7.6.x (opens in a new tab), Fortinet community: high node memory (opens in a new tab), r/fortinet threads on an 80F on 7.4.11 (opens in a new tab), 7.6.7 memory growth (opens in a new tab) and a 50G HA pair on 7.6.7 (opens in a new tab).
Sources
- https://docs.fortinet.com/document/fortigate/7.4.12/fortios-release-notes/236526/known-issues (opens in a new tab)
- https://docs.fortinet.com/document/fortigate/7.4.13/fortios-release-notes/289806/resolved-issues (opens in a new tab)
- https://docs.fortinet.com/document/fortigate/7.6.6/fortios-release-notes/236526/known-issues (opens in a new tab)
- https://docs.fortinet.com/document/fortigate/7.6.8/fortios-release-notes/289806/resolved-issues (opens in a new tab)
- https://community.fortinet.com/fortigate-3/troubleshooting-tip-conserve-mode-triggered-by-node-process-in-fortios-v7-4-x-and-v7-6-x-229137 (opens in a new tab)
- https://community.fortinet.com/fortigate-3/troubleshooting-tip-high-memory-usage-of-node-process-114615 (opens in a new tab)
- https://www.reddit.com/r/fortinet/comments/1szv721/possible_node_memory_leak_on_80f_running_7411/ (opens in a new tab)
- https://www.reddit.com/r/fortinet/comments/1vo0w9z/memory_and_cpu_usage_increase_after_upgrading_to/ (opens in a new tab)
- https://www.reddit.com/r/fortinet/comments/1vdryss/fortigate_50g_767_ha_pair_keep_going_into/ (opens in a new tab)
- https://docs.fortinet.com/document/fortigate/7.6.8/fortios-release-notes/236526/known-issues (opens in a new tab)
- https://docs.fortinet.com/document/fortigate/7.6.8/fortios-release-notes/545418/csf-downstream-gui-login-fails-with-security-fabric-saml-sso (opens in a new tab)
- https://community.fortinet.com/fortigate-3/administrator-sso-authentication-fails-after-upgrade-to-fortios-7-6-8-230826 (opens in a new tab)
- https://www.fortinet.com/blog/ciso-collective/fortinet-releases-security-hardening-release-for-multiple-products (opens in a new tab)