dbcve.org
FortiproxyApplication · Fortinet

CVE-2026-59837

MEDIUM · 6.6 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 1.8.3 / 7.4.2 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable Zero-click 5 weeks old

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

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 · moderate confidence

A stack-based buffer overflow in Fortinet FortiOS, FortiPAM, and FortiProxy allows a privileged authenticated attacker to execute arbitrary code via crafted HTTP requests, but only after bypassing stack protection (canaries) and ASLR security mechanisms.

MitigationApply vendor-supplied firmware patches for FortiOS, FortiPAM, and FortiProxy; restrict administrative access to trusted IPs only; monitor for indicators of compromise and anomalous HTTP traffic patterns.

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
FortiproxyApplication
Affected:>= 7.2.0, < 7.4.14
FortiosOperating system
Affected:>= 7.2.0, < 7.4.2
FortipamOperating system
Affected:>= 1.0.0, < 1.8.3

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
High
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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 the Fortinet product running in your environment
    Access the device CLI or web UI and run the command: get system status (CLI) or check System > FortiView > Dashboard in the web UI to see the product name and model
    Affected if The device is not FortiOS, FortiPAM, or FortiProxy (the CVE does not apply)
  2. Determine the installed firmware version
    Run: get system status in the Fortinet CLI. The output will display the Firmware Version (for FortiOS), FortiPAM Version, or FortiProxy Version
    Affected if The version falls within these ranges: FortiOS >= 7.2.0 and < 7.4.2, FortiPAM >= 1.0.0 and < 1.8.3, FortiProxy >= 7.2.0 and < 7.4.14
  3. Verify if HTTP/HTTPS administrative interface is exposed externally
    Review your network firewall rules and Fortinet firewall policy settings to confirm whether ports 80/443 or the management interface (port1 by default) are accessible from untrusted networks or the internet
    Affected if The management interface is reachable from untrusted IP addresses (the vulnerability requires a network-accessible authenticated attacker)
  4. Confirm the attacker would need privileged authentication
    Review admin user accounts and their privilege level in FortiOS/FortiPAM/FortiProxy via: get admin user (CLI) or check System > Admin > Administrators in the web UI
    Affected if Any privileged admin account exists on the system (the CVE requires an authenticated attacker with privileges to send the crafted HTTP requests)

You are affected if you run FortiOS 7.2.0 through 7.4.1, FortiPAM 1.0.0 through 1.8.2, or FortiProxy 7.2.0 through 7.4.13, and your management interface is accessible to an attacker who has obtained privileged admin credentials.

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 1.8.3 / 7.4.2 / 7.4.14 or later
Fixed in 1.8.37.4.27.4.14
Interim mitigation

Apply vendor-supplied firmware patches for FortiOS, FortiPAM, and FortiProxy; restrict administrative access to trusted IPs only; monitor for indicators of compromise and anomalous HTTP traffic patterns.

Recommended fix High confidence

FortiOS >= 7.4.2, FortiProxy >= 7.4.14, FortiPAM >= 1.8.3

  1. For FortiOS: Upgrade to version 7.4.2 or later
  2. For FortiProxy: Upgrade to version 7.4.14 or later
  3. For FortiPAM: Upgrade to version 1.8.3 or later
  4. After upgrading, verify the new version is running with 'get system status' command
  5. Confirm the vulnerability is resolved by reviewing FortiGuard release notes for the installed version
Caveat Upgrading major versions may require downtime and configuration review; always test in a staging environment before production deployment

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

Fix this in Fortiproxy Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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