Cyber Resilience

CVE-2025-54820

Memory Safety in Fortinet Fortimanager 6.4.0 – 7.2.11

Memory Safety
Published
10 March 2026
Modified
12 March 2026
Patch / advisory
View advisory
CVSS Score v3.1 8.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0087 56th percentile
Risk Priority 61 floored blend · peak EPSS

Summary

CVE-2025-54820 is a high-severity Stack-based Buffer Overflow (CWE-121) vulnerability in Fortinet Fortimanager. Its CVSS base score is 8.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 44% 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-54820 is a stack-based buffer overflow vulnerability (CWE-121 and CWE-787) affecting Fortinet FortiManager versions 7.4.0 through 7.4.2, 7.2.0 through 7.2.10, and all versions of 6.4. The flaw arises in a service that, when enabled, can be triggered by crafted requests, potentially leading to unauthorized command execution. Published on 2026-03-10 with a CVSS v3.1 base score of 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H), it highlights high-impact risks across confidentiality, integrity, and availability despite requiring high attack complexity.

A remote unauthenticated attacker can exploit this vulnerability over the network by sending specially crafted requests to the vulnerable service on an affected FortiManager instance. Successful exploitation enables execution of unauthorized commands, though it hinges on the attacker's ability to bypass stack protection mechanisms. No privileges, user interaction, or scope changes are required, making it viable against internet-exposed or internally accessible FortiManager systems where the service is active.

The Fortinet PSIRT advisory at https://fortiguard.fortinet.com/psirt/FG-IR-26-098 details mitigation steps and affected versions. Security practitioners should consult this reference for patch availability, workarounds, and configuration guidance to disable the service if feasible.

EU & UK References

Vulnerability Data

A Stack-based Buffer Overflow vulnerability [CWE-121] vulnerability in Fortinet FortiManager 7.4.0 through 7.4.2, FortiManager 7.2.0 through 7.2.10, FortiManager 6.4 all versions may allow a remote unauthenticated attacker to execute unauthorized commands via crafted requests, if the service is enabled. The…

more

success of the attack depends on the ability to bypass the stack protection mechanisms.

CWE(s)
CWE-121CWE-787

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1211 Exploitation for Stealth Stealth
Adversaries may exploit vulnerabilities to evade detection by hiding activity, suppressing logging, or operating within trusted or unmonitored components.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-31496Same product: Fortinet Fortimanager
CVE-2024-35276Same product: Fortinet Fortimanager
CVE-2023-33308Same vendor: Fortinet
CVE-2023-29182Same vendor: Fortinet
CVE-2023-46720Same vendor: Fortinet
CVE-2023-25602Same vendor: Fortinet
CVE-2024-26010Same vendor: Fortinet
CVE-2025-58413Same vendor: Fortinet
CVE-2025-32756Same vendor: Fortinet
CVE-2023-23780Same vendor: Fortinet

Affected Assets

fortinet
fortimanager
6.4.0 — 7.2.11 · 7.4.0 — 7.4.3

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 2 hardening rules · 2 OS baselines
Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and analysis can discover stack-buffer overflows before deployment.

SI-10 Information Input Validation good match

Input validation directly stops untrusted data from exceeding stack buffer bounds.

SI-16 Memory Protection good match

Memory-protection mechanisms limit the ability to execute injected code after a stack overflow.

SA-15 Development Process, Standards, and Tools partial match

Requiring documented secure-development standards and tools can mandate bounds-checked coding practices that avoid the weakness.

SA-8 Security and Privacy Engineering Principles partial match

Secure-engineering principles include bounds-checked coding and safe buffer handling that avoid introducing the flaw.

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.

PR.PS-06 mostly match
prevents

Secure-development practices directly prevent introduction of stack buffer overflows.

ID.RA-01 partial match
prevents

Vulnerability scanning can discover stack buffer overflows but does not prevent their introduction.

PR.PS-02 partial match
prevents

Patching eliminates known instances of the weakness after discovery.

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.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing (fuzzing, static analysis) detects stack overflows before release.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates buffer-safety practices that directly prevent stack overflows.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify buffer-size and input-validation rules.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles include memory-safety and least-privilege stack usage.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly forbid unsafe buffer handling that causes CWE-121.

A.8.32 Change management partial match
prevents

Change management can enforce review gates that catch unsafe memory operations before deployment.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (1 rule)
  • V-248594 OL 8 must implement address space layout randomization (ASLR) to protect its memory from unauthorized code execution. prevents CWE-121
Oracle Linux 9 (1 rule)
  • V-271452 OL 9 must use a Linux Security Module configured to enforce limits on system services. prevents CWE-121

References