dbcve.org
FortiosOperating system · Fortinet

CVE-2025-64157

HIGH · 7.2 CVSS v3.1 Published 2026-02-10
Fix available
A fix is available. Upgrade to 7.4.10 / 7.6.5 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 use of externally-controlled format string vulnerability in Fortinet FortiOS 7.6.0 through 7.6.4, FortiOS 7.4.0 through 7.4.9, FortiOS 7.2.0 through 7.2.11, FortiOS 7.0 all versions allows an authenticated admin to execute unauthorized code or commands via specifically crafted configuration.

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

A format string vulnerability in FortiOS configuration handling allows an authenticated admin to inject format specifiers through specially crafted configuration, potentially reading/writing to memory and executing arbitrary code or commands.

MitigationApply available Fortinet patches for the affected FortiOS versions (7.6.0-7.6.4, 7.4.0-7.4.9, 7.2.0-7.2.11, 7.0). Until patched, enforce least-privilege admin access and monitor for anomalous configuration changes.

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.0, < 7.4.10>= 7.6.0, < 7.6.5

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 FortiOS version
    Run 'get system status' or 'show system version' in FortiOS CLI to retrieve the installed firmware version
    Affected if The version falls within 7.0.0 through 7.4.9 OR 7.6.0 through 7.6.4 (the affected ranges)
  2. Confirm admin account access
    Review admin user accounts using 'get admin user' or check admin profiles via 'get system admin profile' in FortiOS CLI
    Affected if Any authenticated admin account with configuration write privileges exists in the system
  3. Review configuration change logs
    Execute 'execute log filter category 2' to enable config changes, then review logs via 'execute log display' or check FortiAnalyzer logs if available for configuration modification events
    Affected if Recent or anomalous configuration changes are present that were not initiated by authorized administrators
  4. Check for format string anomalies in configuration
    Export current configuration using 'execute backup config' and search for unusual format specifier patterns (%s, %x, %n, etc.) in non-script configuration entries
    Affected if Configuration contains unexpected format specifier sequences in user-defined fields

The environment is affected if FortiOS version is 7.0.0-7.4.9 or 7.6.0-7.6.4 and any authenticated admin with configuration access exists, since exploitation requires both vulnerable version and authenticated admin privileges.

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.10 / 7.6.5 or later
Fixed in 7.4.107.6.5
Interim mitigation

Apply available Fortinet patches for the affected FortiOS versions (7.6.0-7.6.4, 7.4.0-7.4.9, 7.2.0-7.2.11, 7.0). Until patched, enforce least-privilege admin access and monitor for anomalous configuration changes.

Recommended fix High confidence

FortiOS 7.4.10 or later for 7.4.x branch; FortiOS 7.6.5 or later for 7.6.x branch; migrate from 7.0.x to 7.4.10+ or 7.6.5+ (7.0.x is end-of-life)

  1. 1. Identify current FortiOS version by running 'get system status' or viewing the dashboard in FortiOS GUI
  2. 2. If running FortiOS 7.0.x: Plan migration path to 7.4.10 or later (7.0.x is end-of-life)
  3. 3. If running FortiOS 7.4.0-7.4.9: Upgrade to FortiOS 7.4.10 or later
  4. 4. If running FortiOS 7.6.0-7.6.4: Upgrade to FortiOS 7.6.5 or later
  5. 5. Before upgrade, backup configuration using 'execute backup full-config'
  6. 6. Review Fortinet release notes for the target version for any migration requirements
  7. 7. Perform upgrade via FortiOS GUI (System > Firmware) or CLI using 'execute firmware upgrade'
  8. 8. After reboot, verify system status shows the new version and all services are operational
Caveat Review release notes before upgrading; ensure compatibility with other Fortinet appliances in the environment; test configuration on staging device before production deployment

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

Fix this in Fortios Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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