dbcve.org
FortianalyzerApplication · Fortinet

CVE-2026-22572

HIGH · 7.2 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 7.4.8 / 7.6.4 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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 in Fortinet FortiAnalyzer 7.6.0 through 7.6.3, FortiAnalyzer 7.4.0 through 7.4.7, FortiAnalyzer 7.2.2 through 7.2.11, FortiManager 7.6.0 through 7.6.3, FortiManager 7.4.0 through 7.4.7, FortiManager 7.2.2 through 7.2.11 may allow an attacker with knowledge of the admins password to bypass multifactor authentication checks via submitting multiple crafted requests.

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

This is an authentication bypass vulnerability in Fortinet FortiAnalyzer and FortiManager appliances. An attacker who possesses a valid admin password can bypass multifactor authentication by submitting multiple crafted requests, effectively allowing unauthorized access to the administrative interface without completing MFA verification.

MitigationApply vendor-supplied patches for the affected versions (FortiAnalyzer 7.6.4+, 7.4.8+, 7.2.12+ and FortiManager 7.6.4+, 7.4.8+, 7.2.12+). Additionally, implement rate limiting on authentication endpoints and monitor for anomalous authentication patterns as a compensating control.

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.2.2, < 7.4.8>= 7.6.0, < 7.6.4
FortimanagerApplication
Affected:>= 7.2.2, < 7.4.8>= 7.6.0, < 7.6.4
Fortimanager CloudApplication
Affected:>= 7.2.2, < 7.4.8>= 7.6.0, < 7.6.4

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 `get system status` or `get system version` from the FortiAnalyzer or FortiManager CLI to display the firmware version and product name
    Affected if The displayed version falls within >= 7.2.2, < 7.4.8 or >= 7.6.0, < 7.6.4 for FortiAnalyzer, FortiManager, or FortiManager Cloud
  2. Confirm MFA is enabled for admin accounts
    Run `get system admin user` to list admin accounts and check if `two-factor` or `mfa` settings are configured for any account with administrative privileges
    Affected if MFA is enabled on one or more admin accounts and the firmware version is in the affected ranges listed above
  3. Review authentication logs for MFA bypass attempts
    Run `execute log filter category event` then `execute log display` or search authentication logs for failed MFA verification events followed by successful sessions from the same source IP in short succession
    Affected if Logs show authentication attempts that bypassed MFA verification or show incomplete MFA handshakes resulting in authenticated sessions

You are affected if FortiAnalyzer, FortiManager, or FortiManager Cloud is running a version between 7.2.2 and 7.4.8 (exclusive) or between 7.6.0 and 7.6.4 (exclusive) AND MFA is enabled for admin accounts.

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.8 / 7.6.4 or later
Fixed in 7.4.87.6.4
Interim mitigation

Apply vendor-supplied patches for the affected versions (FortiAnalyzer 7.6.4+, 7.4.8+, 7.2.12+ and FortiManager 7.6.4+, 7.4.8+, 7.2.12+). Additionally, implement rate limiting on authentication endpoints and monitor for anomalous authentication patterns as a compensating control.

Recommended fix High confidence

FortiAnalyzer/FortiManager 7.4.8 or 7.6.4 and later

  1. 1. Identify the current FortiAnalyzer/FortiManager version by running: get system status
  2. 2. Confirm the version falls within the affected ranges: 7.2.2-7.2.11, 7.4.0-7.4.7, or 7.6.0-7.6.3
  3. 3. Download the appropriate fixed version from Fortinet Customer Support portal: https://support.fortinet.com/
  4. 4. Review Fortinet release notes for the target version for any known issues or migration requirements
  5. 5. Back up the current configuration using: execute backup all-config <ftp|sftp|tftp> <server> <filepath>
  6. 6. Upload and install the firmware upgrade via Web UI (System > Firmware) or CLI: execute system firmware-upgrade <image-file> tftp <server> <image-name>
  7. 7. After upgrade, verify the new version is running: get system status
  8. 8. Confirm MFA is still properly configured and functioning as expected
Caveat Review Fortinet release notes for any configuration changes or migration steps between your current version and the target version; test in non-production environment first

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

Fix this in Fortianalyzer Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22572 — 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-22572 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