dbcve.org
FortiosOperating system · Fortinet

CVE-2025-22258

HIGH · 7.2 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 1.4.3 / 7.0.17 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
A heap-based buffer overflow in Fortinet FortiSRA 1.5.0, 1.4.0 through 1.4.2, FortiPAM 1.5.0, 1.4.0 through 1.4.2, 1.3.0 through 1.3.1, 1.2.0, 1.1.0 through 1.1.2, 1.0.0 through 1.0.3, FortiProxy 7.6.0 through 7.6.1, 7.4.0 through 7.4.7, FortiOS 7.6.0 through 7.6.2, 7.4.0 through 7.4.6, 7.2.0 through 7.2.10, 7.0.2 through 7.0.16, FortiSwitchManager 7.2.1 through 7.2.5 allows attackers to escalate their privilege via specially crafted http 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 · moderate confidence

A heap-based buffer overflow vulnerability in Fortinet FortiSRA, FortiPAM, FortiProxy, FortiOS, and FortiSwitchManager allows authenticated attackers to escalate privileges via specially crafted HTTP requests. The overflow occurs during HTTP request processing and can be exploited to gain higher-level access.

MitigationApply Fortinet's available security patches for all affected product versions; restrict HTTP/HTTPS management access to trusted IP addresses and implement network segmentation to limit exposure.

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
FortiosOperating system
Affected:>= 7.0.2, < 7.0.17>= 7.2.0, < 7.2.11>= 7.4.0, < 7.4.7>= 7.6.0, < 7.6.3
FortipamOperating system
Affected:>= 1.0.0, < 1.4.3= 1.5.0
FortiproxyApplication
Affected:>= 7.4.0, < 7.4.8>= 7.6.0, < 7.6.2
FortisraApplication
Affected:>= 1.4.0, < 1.4.3= 1.5.0
FortiswitchmanagerApplication
Affected:>= 7.2.1, < 7.2.6

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 the Fortinet product
    Determine which Fortinet product is deployed: FortiOS (FortiGate), FortiPAM, FortiProxy, FortiSRA, or FortiSwitchManager. This can be done via the web UI dashboard, CLI command 'get system status', or by examining the login page and UI elements.
    Affected if The product is any of the five affected: FortiOS, FortiPAM, FortiProxy, FortiSRA, or FortiSwitchManager
  2. Check the installed product version
    Run 'get system status' in the Fortinet CLI or view the version in the web UI dashboard under System > Firmware or About section. Compare the version number to the affected ranges: FortiOS 7.0.2-7.0.16, 7.2.0-7.2.10, 7.4.0-7.4.6, 7.6.0-7.6.2; FortiPAM 1.0.0-1.4.2 and 1.5.0; FortiProxy 7.4.0-7.4.7, 7.6.0-7.6.1; FortiSRA 1.4.0-1.4.2 and 1.5.0; FortiSwitchManager 7.2.1-7.2.5.
    Affected if The installed version falls within any of the listed affected version ranges
  3. Verify if HTTP/HTTPS management is enabled
    In the CLI, run 'get system interface' or 'show system interface' to list management interfaces. Check for HTTP (port 80) or HTTPS (port 443) services. In the web UI, go to Network > Interfaces and verify the Administrative Access settings for each interface.
    Affected if HTTP or HTTPS management access is enabled on any interface, particularly on WAN or untrusted interfaces
  4. Check management access restrictions
    Review the trusted host or allowed IP settings for administrative access. In CLI, use 'show system admin' or examine the admin user configuration for trusted IP definitions. In the web UI, check System > Administrators > Trusted Host.
    Affected if Administrative access is open to any IP (0.0.0.0/0) or to untrusted networks, indicating broader exposure
  5. Confirm if remote authentication is required
    Verify that the affected product requires authentication for HTTP/HTTPS management access. This vulnerability requires authenticated attackers, so confirm that valid credentials exist in the system. Check 'get system admin' in CLI to list admin accounts.
    Affected if Local or remote administrator accounts exist and are active, enabling the authenticated attack vector

You are affected if you run any of the five Fortinet products within the specified version ranges AND have HTTP/HTTPS management access enabled, regardless of whether the management interface is exposed to the internet or internal networks.

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 1.4.3 / 7.0.17 / 7.2.6 or later
Fixed in 1.4.37.0.177.2.6
Interim mitigation

Apply Fortinet's available security patches for all affected product versions; restrict HTTP/HTTPS management access to trusted IP addresses and implement network segmentation to limit exposure.

Recommended fix High confidence

FortiOS 7.0.17+, 7.2.11+, 7.4.7+, or 7.6.3+ | FortiPAM 1.4.3+ | FortiProxy 7.4.8+, 7.6.2+ | FortiSRA 1.4.3+ | FortiSwitchManager 7.2.6+

  1. 1. Identify the Fortinet product and current exact version using the CLI command 'get system status' or via the web UI dashboard
  2. 2. Determine the appropriate fixed version based on your current major version branch (FortiOS 7.0.x → 7.0.17+, FortiOS 7.2.x → 7.2.11+, FortiOS 7.4.x → 7.4.7+, FortiOS 7.6.x → 7.6.3+, FortiPAM → 1.4.3+, FortiProxy 7.4.x → 7.4.8+, FortiProxy 7.6.x → 7.6.2+, FortiSRA → 1.4.3+, FortiSwitchManager 7.2.x → 7.2.6+)
  3. 3. Download the firmware upgrade file from the Fortinet Support Portal (support.fortinet.com) after logging in with valid credentials
  4. 4. Review Fortinet's upgrade guide and release notes for your specific product at docs.fortinet.com
  5. 5. Schedule a maintenance window and back up the current configuration using 'execute backup full-config'
  6. 6. Upload and install the firmware via the web UI (System > Firmware) or CLI: 'execute system firmware upgrade'
  7. 7. After reboot, verify the upgrade was successful with 'get system status' confirming the fixed version number
  8. 8. Test critical functionality to ensure the upgrade did not introduce issues
Caveat Minor point releases within the same major.minor branch typically preserve configuration; however, always review release notes for behavioral changes before upgrading across branches

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

Fix this in Fortios Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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