r/fortinet • u/MM_MarioMichel • Oct 23 '26
Other / General Fortinet Am I the only one with this opinion on the "Fortinet Releases Security Hardening Releases"
I’m all for patching fast and for using AI in product security testing. My concern is the disclosure model of this release, and I’d like to know how others see it.
What happened
On Oct 22 Fortinet shipped FortiOS 8.0.2 / 7.6.8 / 7.4.13 / 7.2.14 plus matching FortiManager and FortiAnalyzer builds. After the CISO blog post, they describe the fixes as critical and high severity.
There are no CVE IDs, no CVSS scores and no advisories. Those are promised for Patch Tuesday, Nov 10. Belgium’s CCB points out that the announcement gives no vulnerability classes or exploitation conditions either.
Fortinet’s reasoning is that attackers can use AI to diff patches and build exploits within hours or days, and that detailed advisories would speed that up.
Why I’m uneasy
The reasoning cuts both ways. Fortinet’s own testing showed that frontier models were very good at diffing firmware versions and writing PoCs for already-fixed bugs. So the diffable patches are public now, while defenders have no advisory to scope risk or write detections. watchTowr’s Yordan Ganchev argued to Cybernews that announcing in advance mainly helps attackers’ patch-diffing tools.
It doesn’t line up with common disclosure practice. Normally advisories ship with the patch, so admins can assess risk, check exposure and justify emergency change windows. “Trust us, it’s critical” is hard to put in front of a change board. I realize Fortinet did something similar in 2023 with CVE-2023-27997, where the release notes didn’t mention it. This time it is an announced policy, though, and it comes with a quarterly cadence.
The patches themselves aren’t smooth.
Threads here report Security Fabric SAML SSO login problems, upgrade-path issues and releases being pulled and re-added, which is worrying for a “patch immediately” message. The 7.6.8 release notes also describe a failing SAML SSO admin login on downstream Fabric devices.
If SSO/MFA-backed admin access breaks after upgrading, admins either lose access or delay the patch. Fortinet’s own interim advice is to enforce MFA for admins.
Known issue 1353958 breaks HTTPS on non-standard ports with deep inspection in all four fixed builds.
There is also this AI comparison thread, which I find worrying.
What I’m not saying
Don’t skip the patches. Internet-facing devices should be updated (backup first, FortiManager/FortiAnalyzer before the FortiGates, admin access restricted).
I’m not calling for no vendor discretion at all.
Questions
Is withholding CVE details for ~3 weeks after shipping patches acceptable to you? Would you accept it from other vendors?
Are you patching now, in stages, or waiting for the first follow-up build?
Has anyone hit the SAML SSO or deep inspection issues in production?



