dbcve.org
FortiwebApplication · Fortinet

CVE-2026-24640

MEDIUM · 6.6 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 7.6.7 / 8.0.3 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 [CWE-121] vulnerability in Fortinet FortiWeb 8.0.0 through 8.0.2, FortiWeb 7.6.0 through 7.6.6, FortiWeb 7.4 all versions, FortiWeb 7.2 all versions, FortiWeb 7.0.2 through 7.0.12 may allow a remote 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 · high confidence

A stack-based buffer overflow vulnerability in FortiWeb's HTTP request processing allows an authenticated attacker to overflow a stack buffer via crafted HTTP requests. Successful exploitation requires bypassing stack protection (canaries) and ASLR, but can lead to arbitrary code or command execution.

MitigationApply vendor-supplied patches for affected FortiWeb versions (8.0.3+, 7.6.7+, or later supported versions). Until patched, limit administrative access to trusted users only and monitor for 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
FortiwebApplication
Affected:>= 7.0.2, <= 7.0.12>= 7.2.0, < 7.6.7>= 8.0.0, < 8.0.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. Determine FortiWeb version
    Run CLI command 'get system status' or 'fortiweb -version' to retrieve the installed FortiWeb version number
    Affected if Version falls within 7.0.2 to 7.0.12, 7.2.0 to 7.6.6, or 8.0.0 to 8.0.2
  2. Confirm HTTP processing is enabled
    Verify FortiWeb is configured to process HTTP traffic (this is typically enabled by default as FortiWeb's primary function)
    Affected if HTTP profiles or virtual servers are configured to handle HTTP requests
  3. Verify authentication is possible
    Check if administrative or user authentication is configured for the FortiWeb management interface or protected applications
    Affected if Authenticated access to FortiWeb or protected back-end servers is possible (required for exploitation)

The environment is affected if FortiWeb version is 7.0.2-7.0.12, 7.2.0-7.6.6, or 8.0.0-8.0.2 AND HTTP processing is enabled AND an attacker can obtain authenticated access to send crafted HTTP requests.

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 7.6.7 / 8.0.3 or later
Fixed in 7.6.78.0.3
Interim mitigation

Apply vendor-supplied patches for affected FortiWeb versions (8.0.3+, 7.6.7+, or later supported versions). Until patched, limit administrative access to trusted users only and monitor for anomalous HTTP traffic patterns.

Recommended fix High confidence

Upgrade to 7.0.13+ for 7.0.x branch, 7.6.7+ for 7.2.x/7.4.x/7.6.x branch, or 8.0.3+ for 8.0.x branch

  1. 1. Identify the currently installed FortiWeb version using: execute get system status
  2. 2. Based on the current version, determine the appropriate upgrade path: - For 7.0.x (7.0.2-7.0.12): upgrade to 7.0.13 or later - For 7.2.x, 7.4.x, 7.6.x (7.2.0-7.6.6): upgrade to 7.6.7 or later - For 8.0.x (8.0.0-8.0.2): upgrade to 8.0.3 or later
  3. 3. Download the appropriate firmware image from Fortinet Customer Support portal (https://support.fortinet.com)
  4. 4. Upload the firmware to FortiWeb via Web UI: System > Firmware > Upload or via CLI: execute restore image
  5. 5. Reboot the FortiWeb device to apply the new firmware
  6. 6. After reboot, verify the version using: execute get system status
  7. 7. Confirm the vulnerability is resolved by checking the new version is at or above the fixed version for your branch
Caveat Review FortiWeb release notes for your upgrade path for any configuration or feature changes between versions

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

Fix this in Fortiweb 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-24640 — 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-24640 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