Fortinet's details wait until November 10
Fortinet named fixed FortiOS versions for an October 22 hardening release. Detailed advisories wait until November 10. An Australian alert knows of no exploitation there.
The short version
No. Fortinet's October 21, 2026 post, for releases on October 22, names fixed FortiOS versions 8.0.2, 7.6.8, 7.4.13, and 7.2.14, and it includes FortiManager and FortiAnalyzer. It says the detailed public advisories wait for Patch Tuesday, November 10. Australia's alert of October 23 says it knows of no exploitation there. Older medium and low notices from October 13 are a different set.
Fixed versions now, details in November
Carl Windsor's October 21 post says a security hardening release for multiple products lands with the October 22 builds. The FortiOS fixed versions in that post are 8.0.2, 7.6.8, 7.4.13, and 7.2.14, each closing a range of earlier numbers in that branch. FortiManager and FortiAnalyzer are named in the same release. The detailed public advisories are deferred to November 10. An advisory is the story when it exists. This week the story is the version list and the date the rest arrives.The advisory is the document.
A patch window is the version, plus a date
Customers who face the internet with these products are the people the post addresses. The window is the fixed build on one side and November 10 on the other. A window without the vulnerability essay is still a window. The essay is what the company says it will publish later. Asked directly, Does Australia report exploitation? The alert reviewed on October 23 says there is no known exploitation in Australia. That sentence is about Australia. It is not a global census. The document named in the sources is the record this page will keep.A window is a version and a date.
Australia's alert is a scope sentence
The Australian Cyber Security Centre's alert, published and reviewed on October 23, says it knows of no exploitation in Australia, that FortiSASE updated on its own, and that FortiManager may need someone to apply the update. More detail, the alert says, is expected on November 10. No known exploitation in one country is not a finding about every network. The document named in the sources is the record this page will keep. The document named in the sources is the record this page will keep.
October 13 is a different pair of notices
Fortinet already had public notices on October 13 for a medium unauthenticated graphical denial-of-service and a low authenticated command-line fault, with their own fixed versions in the 8.0.1 and 7.6.7 neighborhood and earlier. Those identifiers are not the critical set this hardening post is withholding. Mixing them would give a reader a CVE and hide the fact that the new details are not public yet. An identifier only helps when it is the identifier for the issue in front of you. The document named in the sources is the record this page will keep.Use the identifier for this issue.
The thanks line is not a method
The post thanks Anthropic, OpenAI, Google, and SpaceX for frontier-model assistance in the testing. Help Net Security's October 26 headline condenses that thanks into flaws found with AI help. The thanks is the company's. The testing method is not in the post, and it is not reconstructed here. Asked directly, When do the detailed advisories arrive? The post defers them to Patch Tuesday, November 10, 2026. The Australian alert says more detail is expected the same day. The document named in the sources is the record this page will keep.
Who is in scope today
Administrators of internet-facing FortiOS, FortiManager, and FortiAnalyzer in the version ranges the post lists. A network that does not run those products is outside the post. A training exercise that left a sandbox is a different incident and a different brief. Asked directly, Which FortiOS versions does the October 21 post name as fixed? 8.0.2, from 8.0.0 and 8.0.1. 7.6.8, from 7.6.0 through 7.6.7. 7.4.13, from 7.4.0 through 7.4.12. 7.2.14, from 7.2.0 through 7.2.13. The document named in the sources is the record this page will keep.A sandbox miss is a different brief.
What this page will not add
Exploit steps, chaining stories, and differences between patches are not in the October 21 post, because the company says the detailed advisories come on November 10. Writing them early would be invention. A certificate-authority exit is a different control and does not patch a firewall. Asked directly, What else is in the hardening release? FortiManager and FortiAnalyzer, in the same post. FortiSASE, the Australian alert says, was updated automatically, while FortiManager may need a manual update. The document named in the sources is the record this page will keep.A trust-store exit is not this patch.
Help Net Security is the wire account
The October 26 story is why the hardening post is on this morning's security wire. It does not move the fixed builds off October 22, and it does not publish the November 10 details early. The short answer this page will stand on is this: No. Fortinet's October 21, 2026 post, for releases on October 22, names fixed FortiOS versions 8.0.2, 7.6.8, 7.4.13, and 7.2.14, and it includes FortiManager and FortiAnalyzer. It says the detailed public advisories wait for Patch Tuesday, November 10. Australia's alert of October 23 says it knows of no exploitation there. Older medium and low notices from October 13 are a different set.
What November 10 changes
A reader who needs the vulnerability names, the scores, and the conditions will have a document to read on that date, if Fortinet keeps the schedule the post and the Australian alert both give. Until that document exists, the fixed version is the action and the essay is still pending. Asked directly, Are the October 13 notices this same set? No. Those earlier notices were a medium graphical denial-of-service and a low authenticated command-line bug, already public with their own fixed versions. They are not the set whose details Fortinet is holding until November 10.
Sources
The reports this brief is filing. Futureweb did not republish them.
Questions
Which FortiOS versions does the October 21 post name as fixed?
8.0.2, from 8.0.0 and 8.0.1. 7.6.8, from 7.6.0 through 7.6.7. 7.4.13, from 7.4.0 through 7.4.12. 7.2.14, from 7.2.0 through 7.2.13.
What else is in the hardening release?
FortiManager and FortiAnalyzer, in the same post. FortiSASE, the Australian alert says, was updated automatically, while FortiManager may need a manual update.
When do the detailed advisories arrive?
The post defers them to Patch Tuesday, November 10, 2026. The Australian alert says more detail is expected the same day.
Does Australia report exploitation?
The alert reviewed on October 23 says there is no known exploitation in Australia. That sentence is about Australia. It is not a global census.
Are the October 13 notices this same set?
No. Those earlier notices were a medium graphical denial-of-service and a low authenticated command-line bug, already public with their own fixed versions. They are not the set whose details Fortinet is holding until November 10.