dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 30 Jan 2026.
FortianalyzerApplication · Fortinet

CVE-2026-24858

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-27
Fix available
A fix is available. Upgrade to 7.4.10 / 7.4.11 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A FortiCloud SSO authentication bypass vulnerability allows an attacker with a valid FortiCloud account and one registered device to authenticate to other devices registered to different accounts. This occurs due to improper validation of account association during SSO login, enabling unauthorized cross-account device access.

MitigationApply Fortinet patches for the specific product versions (7.6.x, 7.4.x, 7.2.x, 7.0.x) as listed in the advisory. Until patched, consider disabling FortiCloud SSO authentication if operationally feasible, or implement additional monitoring for anomalous cross-account login attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FortianalyzerApplication
Affected:>= 7.0.0, <= 7.0.15>= 7.2.0, <= 7.2.11>= 7.4.0, < 7.4.10>= 7.6.0, < 7.6.6
FortimanagerApplication
Affected:>= 7.0.0, <= 7.0.15>= 7.2.0, <= 7.2.11>= 7.4.0, < 7.4.10>= 7.6.0, < 7.6.6
Fortinac FApplication
Affected:>= 7.6.3, < 7.6.6
FortiproxyApplication
Affected:>= 7.0.0, <= 7.0.22>= 7.2.0, <= 7.2.15>= 7.4.0, <= 7.4.12>= 7.6.0, <= 7.6.4
FortiwebApplication
Affected:>= 7.4.0, <= 7.4.11>= 7.6.0, <= 7.6.6>= 8.0.0, <= 8.0.3
FortiosOperating system
Affected:>= 7.0.0, <= 7.0.18>= 7.2.0, <= 7.2.12>= 7.4.0, < 7.4.11>= 7.6.0, < 7.6.6
Ruggedcom Ape1808 FirmwareOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify product and version
    Run the appropriate command to display the Fortinet product version (for example, 'get system status' or 'fortimanager -v' depending on product). Compare the displayed version number against the affected version ranges provided in the CVE.
    Affected if The installed version falls within any of these ranges: Fortianalyzer 7.0.0-7.0.15, 7.2.0-7.2.11, 7.4.0-7.4.9, 7.6.0-7.6.5; Fortimanager 7.0.0-7.0.15, 7.2.0-7.2.11, 7.4.0-7.4.9, 7.6.0-7.6.5; Fortinac F 7.6.3-7.6.5; Fortiproxy 7.0.0-7.0.22, 7.2.0-7.2.15, 7.4.0-7.4.12, 7.6.0-7.6.4; Fortiweb 7.4.0-7.4.
  2. Verify FortiCloud SSO authentication is enabled
    Locate the SSO authentication configuration for FortiCloud in the product management interface or configuration files. Check whether FortiCloud-based single sign-on authentication is turned on for the device.
    Affected if FortiCloud SSO authentication is currently enabled on the device.
  3. Confirm device is registered to FortiCloud
    Check the device registration status in the FortiCloud console or in the local product configuration to see if the device is linked to a FortiCloud account.
    Affected if The device is registered to a FortiCloud account.

The device is vulnerable if it runs an affected version AND has FortiCloud SSO authentication enabled AND is registered to a FortiCloud account.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.4.10 / 7.4.11 / 7.6.6 or later
Fixed in 7.4.107.4.117.6.6
Interim mitigation

Apply Fortinet patches for the specific product versions (7.6.x, 7.4.x, 7.2.x, 7.0.x) as listed in the advisory. Until patched, consider disabling FortiCloud SSO authentication if operationally feasible, or implement additional monitoring for anomalous cross-account login attempts.

Recommended fix Moderate confidence

Upgrade to the fixed version per Fortinet's advisory: FortiOS 7.4.10+ or 7.6.6+, FortiAnalyzer 7.4.10+ or 7.6.6+, FortiManager 7.4.10+ or 7.6.6+, FortiProxy 7.4.13+ or 7.6.5+, FortiWeb 7.4.12+ or 7.6.7+ or 8.0.4+, FortiNAC-F 7.6.6+

  1. Identify the specific Fortinet product (FortiOS, FortiAnalyzer, FortiManager, FortiProxy, FortiWeb, or FortiNAC-F) and current version running in your environment
  2. Consult FortiGuard (fortiguard.fortinet.com) or the Fortinet PSIRT advisory for the exact fixed version for your product and branch
  3. Upgrade the affected device to the fixed version recommended by Fortinet for your product version branch
  4. After upgrade, verify that FortiCloud SSO authentication settings are configured correctly and test the authentication flow
  5. If immediate upgrade is not possible, consider disabling FortiCloud SSO authentication as a temporary mitigation until the patch can be applied
Caveat Review Fortinet release notes for your product version for any configuration or feature changes that may affect your deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fortianalyzer Exploited in the wild — priority engagement
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-24858 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-24858 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data