Skip to content
Weekly Signal
Live intelligence Updated 19 Aug 2026 · 13:41 UTC

Fortinet, Siemens · Fortianalyzer, FortiManager, Fortinac-f +5 more

CVE-2026-24858

Fortinet Multiple Products Authentication Bypass Using an Alternate Path or Channel Vulnerability

Recommended action

Validate affected assets and exposure now, then remediate on an accelerated schedule. Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

View response plan
CVSS9.8
EPSS85.8%
KEVYes
ExploitationConfirmed exploitation
PatchPatch or guidance available ↓

Assessment

Why it matters

CISA lists this vulnerability as known to be exploited; exploitation is confirmed; EPSS is 85.8%; technical severity is CVSS 9.8.

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.

Who should care

  • Teams operating Fortianalyzer, FortiManager, Fortinac-f +5 more
  • Vulnerability and exposure management teams
  • Security operations teams monitoring exploitation activity

Response plan

What I would do

  1. Confirm whether Fortianalyzer, FortiManager, Fortinac-f +5 more is present in the environment.
  2. Identify affected versions and establish whether vulnerable services are exposed or reachable.
  3. Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
  4. Review relevant security telemetry for evidence of attempted or successful exploitation.
  5. Document the remediation decision and track it to verified completion.

Vendor remediation

Patch and remediation links

Use the vendor source below to confirm the correct fixed version, package or mitigation for your affected product.

Technical details

CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-288
Affected versions
Fortinet Fortianalyzer (Start Including: 7.6.0, End Excluding: 7.6.6); Fortinet FortiManager (Start Including: 7.6.0, End Excluding: 7.6.6); Fortinet Fortinac-f (Start Including: 7.6.3, End Excluding: 7.6.6); Fortinet FortiOS (Start Including: 7.6.0, End Excluding: 7.6.6); Fortinet Fortiproxy (Start Including: 7.6.0, End Including: 7.6.4); Fortinet FortiWeb (Start Including: 8.0.0, End Including: 8.0.3); Fortinet Multiple Products; Siemens Ruggedcom Ape1808 Firmware (Version: -)
Published
27 January 2026
Attack vector
Network
Privileges required
None
User interaction
None

Signal timeline

  1. CVE published
  2. Added to CISA KEV
  3. Latest EPSS score: 85.8%
  4. Signal calculated at 83

External references

Live public intelligence This assessment combines public-source evidence. Validate the affected product, version and exposure against your own environment before making a risk decision.