Cyber Resilience

CVE-2026-59837

Memory Safety in Fortinet Fortiproxy 7.2.0 – 7.4.14

Published
14 July 2026
Modified
15 July 2026
Patch / advisory
CVSS Score v3.1 6.6
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0058 44th percentile
Risk Priority 45 floored blend · peak EPSS

Summary

CVE-2026-59837 is a medium-severity Stack-based Buffer Overflow (CWE-121) vulnerability in Fortinet Fortiproxy. Its CVSS base score is 6.6 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 44th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and SI-16 (Memory Protection) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

A stack-based buffer overflow vulnerability in Fortinet FortiOS 7.4.0 through 7.4.1, FortiOS 7.2 all versions, FortiPAM 1.8.0 through 1.8.2, FortiPAM 1.7 all versions, FortiPAM 1.6 all versions, FortiPAM 1.5 all versions, FortiPAM 1.4 all versions, FortiPAM 1.3 all versions, FortiPAM…

more

1.2 all versions, FortiPAM 1.1 all versions, FortiPAM 1.0 all versions, FortiProxy 7.4.0 through 7.4.13, FortiProxy 7.2 all versions may allow a privileged authenticated attacker who can bypass stack protection and ASLR to execute arbitrary code or commands via crafted HTTP requests.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

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.
Why these techniques?

Stack-based buffer overflow in FortiOS/FortiProxy management interface allows authenticated RCE via crafted HTTP requests, directly enabling exploitation of public-facing applications.

Confidence: HIGH · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-59839Same product: Fortinet Fortios
CVE-2024-35279Same product: Fortinet Fortios
CVE-2024-26009Same product: Fortinet Fortios
CVE-2023-46718Same product: Fortinet Fortios
CVE-2024-55591Same product: Fortinet Fortios
CVE-2026-59840Same product: Fortinet Fortios
CVE-2025-24472Same product: Fortinet Fortios
CVE-2023-42790Same product: Fortinet Fortios
CVE-2024-45324Same product: Fortinet Fortios
CVE-2023-45584Same product: Fortinet Fortios

Affected Assets

fortinet
fortiproxy
7.2.0 — 7.4.14
fortinet
fortios
7.2.0 — 7.4.2
fortinet
fortipam
1.0.0 — 1.8.3

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-10 Information Input Validation
  • SI-16 Memory Protection
  • AC-6 Least Privilege
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

prevent

Directly mitigates CWE-121 by requiring validation of HTTP request lengths and formats before they reach the stack buffer in FortiOS/FortiPAM/FortiProxy.

prevent

Enforces memory protections (e.g., stack canaries, ASLR enforcement) that the attacker must bypass to achieve code execution via the overflow.

prevent

Restricts the set of privileged authenticated accounts that can reach the vulnerable HTTP endpoints, reducing the attack surface for crafted requests.

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.

detects

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

prevents

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

prevents

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

prevents

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

prevents

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

none

Change-management gates can enforce security reviews that catch buffer issues.

References