Called exploited the same day it was disclosed.
Measured from the CVE publication date to the earliest of 3 KEV catalogues that list it.
The life of this vulnerability
- CVE published
- First KEV listingsame day
- Last sighting6mo
Gaps are compressed to equal steps. The elapsed time is printed under each.
Which catalogues call it exploited
- CISA KEVUS federallisted Jan 27, 2026
- EUVDENISA, European Unionlisted Jan 27, 2026
- VulnCheck KEVcommercial researchlisted Jan 27, 2026
- CIRCLaggregator, mirrors the abovelisted Jan 27, 2026, not counted
3 catalogues list it. CIRCL aggregates the others and is shown but not counted.
Public exploitation evidence
- reported exploitationcyble.com/reports/H1-2026-Global-Threat-Landscape-Report.pdf
- reported exploitationwww.levelblue.com/blogs/spiderlabs-blog/ttp-briefing-q2-2026
- reported exploitationwww.wiz.io/blog/agentless-threat-hunting-fortigate
- reported exploitationblog.qualys.com/vulnerabilities-threat-research/2026/07/08/f
- reported exploitationwww.techgines.com/post/fortibleed-fortigate-credential-compr
- reported exploitationwww.trendmicro.com/vinfo/gb/security/news/cybercrime-and-dig
11 public reports collected from VulnCheck and CIRCL, first on Jan 27, 2026. Each links to its original source. We have not verified them.
Description
Fortinet FortiAnalyzer, FortiManager, FortiOS, and FortiProxy contain an authentication bypass using an alternate path or channel that could allow an attacker with a FortiCloud account and a registered device to log into other devices registered to other accounts, if FortiCloud SSO authentication is enabled on those devices.
Required action (CISA)
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
