Skip to content
OpenAdvisories
Critical · 9.4 Known exploited Public exploit CVE-2026-24858 EUVD-2026-4712GHSA-2x38-48vp-w23x

An Authentication Bypass Using an Alternate Path or Channel vulnerability [CWE-288] vulnerability in Fortinet FortiAnalyzer 7.6.0 through 7…

Published Jan 27, 2026 · Updated Jun 9, 2026 · Assigned by fortinet

Vendor: Fortinet Product: FortiAnalyzer Product: FortiManager Product: FortiNAC-F Product: FortiOS Product: FortiProxy Product: FortiWeb Category: Network devices

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.

Affected products

VendorProductAffectedFixed
Fortinet FortiWeb 8.0.0 – ≤ 8.0.3, 7.6.0 – ≤ 7.6.6, 7.4.0 – ≤ 7.4.11 —
Fortinet FortiNAC-F 7.6.3 – ≤ 7.6.5 —
Fortinet FortiOS 7.6.0 – ≤ 7.6.5, 7.4.0 – ≤ 7.4.10, 7.2.0 – ≤ 7.2.12, 7.0.0 – ≤ 7.0.18 —
Fortinet FortiAnalyzer 7.6.0 – ≤ 7.6.5, 7.4.0 – ≤ 7.4.9, 7.2.0 – ≤ 7.2.11, 7.0.0 – ≤ 7.0.15 —
Fortinet FortiProxy 7.6.0 – ≤ 7.6.4, 7.4.0 – ≤ 7.4.12, 7.2.0 – ≤ 7.2.15, 7.0.0 – ≤ 7.0.22 —
Fortinet FortiManager 7.6.0 – ≤ 7.6.5, 7.4.0 – ≤ 7.4.9, 7.2.0 – ≤ 7.2.11, 7.0.0 – ≤ 7.0.15 —

Public exploits

Exploit or proof-of-concept code for this vulnerability is publicly available, which lowers the bar for attackers. Treat it as a reason to patch sooner.

Third-party code, not reviewed by us. Public PoCs are sometimes fake or contain malware. Read the code first and run it only in an isolated lab, against systems you are authorised to test.

GitHub 5 repositories

Sources: PoC-in-GitHub, Metasploit Framework, Exploit-DB — updated daily. Only links are listed; no exploit code is hosted here.

Advisories 5

References