dbcve.org
FortiwebApplication · Fortinet

CVE-2026-24641

MEDIUM · 6.5 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 →
71/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 NULL Pointer Dereference vulnerability [CWE-476] 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 all versions may allow an authenticated attacker to crash the HTTP daemon 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 NULL Pointer Dereference vulnerability in FortiWeb's HTTP daemon allows authenticated attackers to crash the service by sending specially crafted HTTP requests. The flaw exists across versions 7.0 through 8.0.2, indicating a persistent code-level issue in request handling logic.

MitigationApply the vendor-supplied FortiWeb patches for the respective version branches (7.0.x, 7.2.x, 7.4.x, 7.6.x, or 8.0.x). If patches are unavailable, consider restricting administrative access to trusted IP addresses and implementing rate limiting on the management interface.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Confirm FortiWeb deployment
    Identify whether FortiWeb appliances or virtual machines are running in your environment. Check for FortiWeb processes or services on known FortiWeb systems.
    Affected if FortiWeb is not present in your environment - you are not affected.
  2. Determine installed FortiWeb version
    Log into the FortiWeb CLI and run the command: get system status. Alternatively, check the web UI under Dashboard > System Information > Firmware Version.
    Affected if The installed version falls within 7.0.0 through 7.6.6, or 8.0.0 through 8.0.2 - your version is within the affected range.
  3. Check if HTTP/HTTPS management interface is enabled
    In FortiWeb CLI, run: show system interface. Look for management interfaces with HTTP or HTTPS enabled. Alternatively, check via web UI under Network > Interfaces.
    Affected if HTTP or HTTPS management access is enabled on any interface - the vulnerable HTTP daemon is exposed.
  4. Review administrative access controls
    Check admin user accounts and access profiles using: show system admin. Verify which IP addresses or ranges are permitted for administrative access.
    Affected if Administrative accounts can be accessed from untrusted networks - an attacker could potentially authenticate and trigger the vulnerability.

Your environment is affected if FortiWeb versions 7.0.0-7.6.6 or 8.0.0-8.0.2 are running with the HTTP management interface exposed to network locations where authenticated attackers could send crafted 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 the vendor-supplied FortiWeb patches for the respective version branches (7.0.x, 7.2.x, 7.4.x, 7.6.x, or 8.0.x). If patches are unavailable, consider restricting administrative access to trusted IP addresses and implementing rate limiting on the management interface.

Recommended fix High confidence

Upgrade to FortiWeb 7.6.7 or later for 7.x branch, or FortiWeb 8.0.3 or later for 8.x branch

  1. 1. Identify the current FortiWeb version by navigating to System > FortiView > Status or using the CLI command 'get system status'.
  2. 2. For FortiWeb 7.6.x deployments: Plan upgrade to version 7.6.7 or later.
  3. 3. For FortiWeb 8.0.x deployments: Plan upgrade to version 8.0.3 or later.
  4. 4. Before upgrading, backup the FortiWeb configuration via System > Maintenance > Backup & Restore or CLI command 'execute backup config'.
  5. 5. Download the appropriate firmware from Fortinet Customer Support portal (https://support.fortinet.com/).
  6. 6. Upload and install the firmware via System > Firmware or CLI command 'execute system firmware upgrade'.
  7. 7. After upgrade, verify the HTTP daemon is running and the new version is applied using 'get system status'.
  8. 8. Test that legitimate HTTP traffic is processing correctly after the upgrade.
Caveat Review Fortinet release notes for 7.6.7 and 8.0.3 for any configuration or feature changes that may affect your deployment

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

Fix this in Fortiweb Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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