CVE-2026-59837
Analyzed Analyzed - Analysis Complete

Stack-Based Buffer Overflow in Fortinet FortiOS and FortiProxy

Vulnerability report for CVE-2026-59837, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-14

Last updated on: 2026-07-15

Assigner: Fortinet, Inc.

Description

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 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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-14
Last Modified
2026-07-15
Generated
2026-08-04
AI Q&A
2026-07-14
EPSS Evaluated
2026-08-02
NVD
EUVD

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
fortinet fortiproxy From 7.2.0 (inc) to 7.4.14 (exc)
fortinet fortios From 7.2.0 (inc) to 7.4.2 (exc)
fortinet fortipam From 1.0.0 (inc) to 1.8.3 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-121 A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-59837 is a stack-based buffer overflow vulnerability found in multiple Fortinet products, including FortiOS, FortiPAM, and FortiProxy.

A stack-based buffer overflow occurs when a program writes more data to a buffer located on the stack than it can hold, leading to memory corruption. In this case, the vulnerability allows a privileged authenticated attacker to bypass stack protection mechanisms like ASLR (Address Space Layout Randomization) and execute arbitrary code or commands.

The attacker must be authenticated with privileged access and craft malicious HTTP requests to exploit this flaw. Successful exploitation could result in unauthorized code execution on the affected system.

Detection Guidance

Detecting this vulnerability requires checking for the presence of affected Fortinet products and their versions on your network or system. Since the vulnerability involves crafted HTTP requests, monitoring network traffic for unusual or malformed HTTP requests to Fortinet devices may indicate exploitation attempts.

  • Identify Fortinet devices: Use network scanning tools like Nmap to detect Fortinet devices. Example command: nmap -p 80,443,8080 --open -sV <network_range> | grep -i fortinet
  • Check device versions: Log in to the Fortinet device's admin interface or use CLI commands to verify the version. For FortiOS, use: get system status | grep Version. For FortiPAM or FortiProxy, refer to their respective admin interfaces or CLI documentation for version checks.
  • Monitor logs: Review logs for unusual HTTP requests or authentication attempts. Fortinet devices typically log such events in their system logs or security event logs.
  • Use vulnerability scanners: Run vulnerability scanning tools like Nessus, OpenVAS, or Fortinet's own FortiScanner to detect the presence of this CVE on your devices.
Impact Analysis

If you are using any of the affected Fortinet products (FortiOS, FortiPAM, or FortiProxy), this vulnerability could have serious consequences.

  • An attacker with privileged access could execute arbitrary code or commands on your system, potentially gaining full control over the affected device.
  • This could lead to unauthorized access to sensitive data, disruption of services, or further compromise of your network infrastructure.
  • Since the vulnerability involves crafted HTTP requests, it could be exploited remotely if the attacker has network access to the vulnerable system.

The CVSS base score of 6.6 indicates a medium severity, but the impact is high for confidentiality, integrity, and availability if successfully exploited.

Compliance Impact

This vulnerability could impact compliance with several common standards and regulations, depending on the context of your organization.

  • GDPR (General Data Protection Regulation): If the affected system processes or stores personal data of EU citizens, a successful exploit could lead to unauthorized access or data breaches. This may result in non-compliance with GDPR's data protection and breach notification requirements.
  • HIPAA (Health Insurance Portability and Accountability Act): For organizations handling protected health information (PHI), exploitation of this vulnerability could lead to unauthorized access to PHI, violating HIPAA's security and privacy rules.
  • Other standards like PCI DSS (Payment Card Industry Data Security Standard) could also be affected if the vulnerable system processes payment card data, as unauthorized code execution could compromise cardholder data security.

Failure to patch or mitigate this vulnerability could result in regulatory penalties, legal liabilities, and reputational damage if a breach occurs.

Mitigation Strategies

To mitigate this vulnerability, follow these immediate steps:

  • Apply patches: Update affected Fortinet products to the latest patched versions as soon as they are available. Fortinet typically releases security advisories with patch information.
  • Restrict access: Limit access to the administrative interfaces of Fortinet devices to trusted IP addresses only. Use firewall rules or access control lists (ACLs) to enforce this.
  • Disable unnecessary services: If certain HTTP services or features are not required, disable them to reduce the attack surface.
  • Enable stack protection and ASLR: Ensure that stack protection and Address Space Layout Randomization (ASLR) are enabled on the affected devices. This may require configuration changes or firmware updates.
  • Monitor for exploitation attempts: Set up alerts for suspicious activity, such as repeated failed login attempts or unusual HTTP requests, and review logs regularly.
  • Segment your network: Isolate Fortinet devices in a dedicated network segment to limit the potential impact of an exploit.
  • Follow Fortinet's advisories: Refer to Fortinet's official security advisories for specific mitigation steps and updates related to this CVE.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-59837. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart