LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24858: An Authentication Bypass Using an Alternate Path or Channel vulnerability [CWE-288] vulnerability in Fortin...

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.

CriticalCVSS 9.4Known exploitedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-24858 is a critical Fortinet authentication bypass affecting multiple Fortinet security products when FortiCloud SSO is enabled. A person with a FortiCloud account and registered device may be able to access devices registered to other accounts. Because CISA lists it as known exploited, affected environments should treat this as urgent.

Executive priority

Treat this as an emergency Fortinet remediation item. It affects security infrastructure, has a critical score, and is KEV-listed. Prioritize assets with FortiCloud SSO enabled and management interfaces reachable from untrusted networks.

Technical view

The issue is CWE-288, authentication bypass using an alternate path or channel. Affected ranges include FortiOS, FortiManager, FortiAnalyzer, FortiProxy, FortiWeb, and FortiNAC-F. The CVSS 3.1 score is 9.4 with network access, low complexity, no privileges, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is highest where affected Fortinet versions use FortiCloud SSO. The bundle does not prove exposure for devices without FortiCloud SSO enabled. Internet-facing administration or broadly reachable management planes would increase business risk.

Exploitation context

Active exploitation is supported by the CISA KEV reference in the source bundle. Fortinet also published analysis of SSO abuse on FortiOS. The bundle does not include exploit mechanics, affected tenant counts, or confirmed exploitation against every listed product.

Researcher notes

The key exposure condition is FortiCloud SSO enabled on affected versions. The source bundle supports broad product impact and active exploitation, but does not provide safe validation probes, exploit details, or complete fixed-version mapping in the supplied text.

Mitigation direction

  • Identify affected Fortinet products and versions across the environment.
  • Confirm whether FortiCloud SSO is enabled on each device.
  • Apply Fortinet PSIRT fixed releases or vendor-approved workarounds for FG-IR-26-060.
  • If upgrade is delayed, assess disabling FortiCloud SSO using vendor guidance.
  • Restrict administrative access paths and review FortiCloud SSO authentication monitoring.

Validation and detection

  • Compare deployed versions against the affected ranges in CVE-2026-24858.
  • Verify FortiCloud SSO configuration per device and account.
  • Check CISA KEV status for required remediation handling.
  • Review authentication logs for unexpected FortiCloud SSO access.
  • Confirm remediation against Fortinet PSIRT FG-IR-26-060.
Prepared
Confidence
high
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-288: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-24858 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.4 (3.1)
Known Exploited
Yes
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
4Timeline events
2ADP providers
5Source links

CISA KEV status

Status
Known exploited
Source
CISA-ADP
Date added
KEV reference

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: activeAutomatable: yesTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.4CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:H/RL:O/RC:C3.95.9fortinet

Vulnerability scoring details

Base CVSS 3.1 score

9.4Critical
CVSS 3.1 vector shape for CVE-2026-24858Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. Added to KEVCISA-ADP

    CISA Known Exploited Vulnerabilities metadata lists this CVE as known exploited.

  2. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvcother:kev
siemens-SADPADP container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
FortinetFortiWeb8.0.0, 7.6.0, 7.4.0unaffected
FortinetFortiNAC-F7.6.3unaffected
FortinetFortiOS7.6.0, 7.4.0, 7.2.0, 7.0.0unaffected
FortinetFortiAnalyzer7.6.0, 7.4.0, 7.2.0, 7.0.0unaffected
FortinetFortiProxy7.6.0, 7.4.0, 7.2.0, 7.0.0unaffected
FortinetFortiManager7.6.0, 7.4.0, 7.2.0, 7.0.0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-288 · source CWE mapping

Authentication Bypass Using an Alternate Path or Channel

Authentication Bypass Using an Alternate Path or Channel represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.