Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Exploited in the wild

CISA lists this vulnerability in its Known Exploited Vulnerabilities catalog as Fortinet Multiple Products Authentication Bypass Using an Alternate Path or Channel Vulnerability.

Added
27 Jan 2026
Fix due (US federal)
30 Jan 2026
Used by ransomware
Not known

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

ENISA's EU Vulnerability Database lists it as exploited, from CISA's KEV, since 27 Jan 2026.

Public exploit

An exploit or proof of concept is public: anyone can try it against an unpatched system. CISA's SSVC rates its exploitation: it is being exploited.

Timeline

  1. ID reserved

    By fortinet

  2. Published

  3. Added to CISA KEV

    Known exploited in the wild

  4. · 4 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-24858, by who scored it
Scored byCVSSScoreVector
fortinetCNA (assigner)3.1Critical9.4CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:H/RL:O/RC:C
NVDNVD · Analyzed3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
86.6% · top 0.3% of all CVEs (12 Nov 2026)
CISA SSVC
Exploitation: active · Automatable: yes · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.4.

Affected products

  • Fortinet · FortiWeb

    • affected 8.0.0 – ≤ 8.0.3
    • affected 7.6.0 – ≤ 7.6.6
    • affected 7.4.0 – ≤ 7.4.11

  • Fortinet · FortiNAC-F

    • affected 7.6.3 – ≤ 7.6.5

  • Fortinet · FortiOS

    • affected 7.6.0 – ≤ 7.6.5
    • affected 7.4.0 – ≤ 7.4.10
    • affected 7.2.0 – ≤ 7.2.12
    • affected 7.0.0 – ≤ 7.0.18

  • Fortinet · FortiAnalyzer

    • affected 7.6.0 – ≤ 7.6.5
    • affected 7.4.0 – ≤ 7.4.9
    • affected 7.2.0 – ≤ 7.2.11
    • affected 7.0.0 – ≤ 7.0.15

  • Fortinet · FortiProxy

    • affected 7.6.0 – ≤ 7.6.4
    • affected 7.4.0 – ≤ 7.4.12
    • affected 7.2.0 – ≤ 7.2.15
    • affected 7.0.0 – ≤ 7.0.22

  • Fortinet · FortiManager

    • affected 7.6.0 – ≤ 7.6.5
    • affected 7.4.0 – ≤ 7.4.9
    • affected 7.2.0 – ≤ 7.2.11
    • affected 7.0.0 – ≤ 7.0.15

What to do

Solution: Upgrade to upcoming FortiOS version 8.0.0 or above Upgrade to FortiOS version 7.6.6 or above Upgrade to FortiOS version 7.4.11 or above Upgrade to FortiOS version 7.2.13 or above Upgrade to FortiOS version 7.0.19 or above Upgrade to upcoming FortiManager version 8.0.0 or above Upgrade to FortiManager version 7.6.6 or above Upgrade to FortiManager version 7.4.10 or above Upgrade to FortiManager version 7.2.12 or above Upgrade to FortiManager version 7.0.16 or above Upgrade to FortiAnalyzer version 7.6.6 or above Upgrade to FortiAnalyzer version 7.4.10 or above Upgrade to FortiAnalyzer version 7.2.12 or above Upgrade to FortiAnalyzer version 7.0.16 or above Upgrade to FortiProxy version 7.6.5 or above Upgrade to FortiProxy version 7.4.13 or above Upgrade to FortiProxy version 7.2.16 or above Upgrade to FortiProxy version 7.0.23 or above Upgrade to FortiWeb version 8.0.4 or above Upgrade to FortiWeb version 7.6.7 or above Upgrade to FortiWeb version 7.4.12 or above Upgrade to FortiNAC-F version 7.6.6 or above Upgrade to FortiSwitchManager version 7.2.9 or above Upgrade to FortiSwitchManager version 7.0.8 or above

References

References4

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-24858 badge
[![CVE-2026-24858](https://cveledger.app/badge/CVE-2026-24858.svg)](https://cveledger.app/cve/CVE-2026-24858)

Record last updated .