FortiManager and FortiAnalyzer

CVE-2026-22575: Improper access control in FortiManager, FortiManager Cloud

An improper access control vulnerability in Fortinet FortiManager 7.6.0 through 7.6.4, FortiManager 7.4.0 through 7.4.10, FortiManager 7.2 all versions, FortiManager Cloud 7.6.2 through 7.6.4, FortiManager Cloud 7.4.1 through 7.4.10, FortiManager Cloud 7.2 all versions may allow an administrator to bypass the approval process for workflow sessions via crafted HTTP or HTTPs requests.

Published

ExploitedNot in CISA KEV
Ransomware useNot reportedPer CISA
SeverityMEDIUMCVSS 3.1 4.7
EPSS0.24%Chance of exploitation in 30 days
Public exploitNot tracked
FixAvailable

Automatic summary from the vendor's CVE record. We haven't written a full analysis of this vulnerability yet.

Affected and fixed versions

Product / branchFixed in
FortiManager 7.6.0 to 7.6.47.6.5 or later
FortiManager 7.4.0 to 7.4.107.4.11 or later
FortiManager 7.2.0 to 7.2.12Upgrade past 7.2.12; see the advisory
FortiManager 7.0.0 to 7.0.16Upgrade past 7.0.16; see the advisory
FortiManager 6.4.0 to 6.4.15Upgrade past 6.4.15; see the advisory
FortiManager Cloud 7.6.2 to 7.6.47.6.5 or later
FortiManager Cloud 7.4.1 to 7.4.107.4.11 (upcoming) or later
FortiManager Cloud 7.2.1 to 7.2.12Upgrade past 7.2.12; see the advisory
FortiManager Cloud 7.0.1 to 7.0.16Upgrade past 7.0.16; see the advisory
FortiManager Cloud 6.4.1 to 6.4.7Upgrade past 6.4.7; see the advisory

Always confirm against the vendor advisory, which lists every fixed hotfix.

What it is

An improper access control vulnerability in Fortinet FortiManager 7.6.0 through 7.6.4, FortiManager 7.4.0 through 7.4.10, FortiManager 7.2 all versions, FortiManager Cloud 7.6.2 through 7.6.4, FortiManager Cloud 7.4.1 through 7.4.10, FortiManager Cloud 7.2 all versions may allow an administrator to bypass the approval process for workflow sessions via crafted HTTP or HTTPs requests.

Sources

KEV status, EPSS score and vendor data refreshed automatically, last on 10 Oct 2026.

Get alerts

A notification when we publish a new analysis or a covered vendor gets a new actively exploited CVE. No account, no email.