CVE-2025-64157
Fortinet Fortios 7.0.0 – 7.4.10
Raw vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2025-64157 is a medium-severity Use of Externally-Controlled Format String (CWE-134) vulnerability in Fortinet Fortios. Its CVSS base score is 6.7 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 31% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-64157 is a use of externally-controlled format string vulnerability (CWE-134) in Fortinet FortiOS. The affected versions include FortiOS 7.6.0 through 7.6.4, 7.4.0 through 7.4.9, 7.2.0 through 7.2.11, and all versions of FortiOS 7.0. It carries a CVSS v3.1 base score of 6.7 (AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H), indicating medium severity with high impacts across confidentiality, integrity, and availability.
An authenticated administrator with local access can exploit the vulnerability by submitting specifically crafted configuration data. Successful exploitation allows execution of unauthorized code or commands on the affected system.
Mitigation details are provided in the Fortinet PSIRT advisory at https://fortiguard.fortinet.com/psirt/FG-IR-25-795.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-207129
Vulnerability Data
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and static analysis can discover format-string vulnerabilities before deployment.
Input validation can reject or sanitize externally supplied format strings before they reach formatting functions.
Secure development standards and tools can mandate use of static format strings or safe formatting APIs.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect format-string vulnerabilities before release.
Secure SDLC mandates input validation and safe API usage that can prevent externally-controlled format strings.
Application security requirements can specify safe formatting functions and ban uncontrolled format strings.
Secure architecture principles discourage dangerous string-handling patterns that lead to format-string issues.
Secure coding standards directly forbid the use of untrusted format strings and prescribe safe alternatives.