dbcve.org
FortiosOperating system · Fortinet

CVE-2024-26010

HIGH · 7.5 CVSS v3.1 Published 2024-06-11
Fix available
A fix is available. Upgrade to 7.0.4 / 7.0.15 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

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 in Fortinet FortiPAM version 1.2.0, 1.1.0 through 1.1.2, 1.0.0 through 1.0.3, FortiWeb, FortiAuthenticator, FortiSwitchManager version 7.2.0 through 7.2.3, 7.0.1 through 7.0.3, FortiOS version 7.4.0 through 7.4.3, 7.2.0 through 7.2.7, 7.0.0 through 7.0.14, 6.4.0 through 6.4.15, 6.2.0 through 6.2.16, 6.0.0 through 6.0.18, FortiProxy version 7.4.0 through 7.4.2, 7.2.0 through 7.2.9, 7.0.0 through 7.0.15, 2.0.0 through 2.0.13, 1.2.0 through 1.2.13, 1.1.0 through 1.1.6, 1.0.0 through 1.0.7 allows attacker to execute unauthorized code or commands via specially crafted packets.

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

Stack-based buffer overflow in Fortinet FortiPAM, FortiWeb, FortiAuthenticator, FortiSwitchManager, FortiOS, and FortiProxy allows remote attackers to execute unauthorized code or commands via specially crafted packets. The overflow occurs in the stack memory region, potentially allowing attackers to overwrite return addresses and inject malicious code.

MitigationApply vendor-supplied patches from Fortinet for the specific affected product versions. For FortiOS/FortiProxy, upgrade to versions 7.4.4+, 7.2.8+, 7.0.15+, 6.4.16+, 6.2.17+, 6.0.19+. For FortiSwitchManager, upgrade to 7.2.4+ or 7.0.4+. For FortiPAM, upgrade to 1.2.1 or later.

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
FortiosOperating system
Affected:>= 6.0.0, < 7.0.15>= 7.2.0, < 7.2.8>= 7.4.0, < 7.4.4
FortipamOperating system
Affected:>= 1.0.0, <= 1.3.0
FortiproxyApplication
Affected:>= 1.0.0, < 7.0.17>= 7.2.0, < 7.2.10>= 7.4.0, < 7.4.4
FortiswitchmanagerApplication
Affected:>= 7.0.1, < 7.0.4>= 7.2.0, < 7.2.4

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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 in use
    Determine which Fortinet product is deployed: FortiOS (FortiGate), FortiProxy, FortiPAM, FortiSwitchManager, FortiWeb, or FortiAuthenticator. Check the device model or management interface to confirm the product name.
    Affected if Any of the listed Fortinet products are in use
  2. Retrieve the installed FortiOS version
    For FortiOS/FortiGate, run the CLI command: `get system status` or `fwmtk sys version`. Alternatively, check the FortiGate GUI under Dashboard > Status or System > Firmware.
    Affected if The version is 6.0.0 or later and falls within < 7.0.15, >= 7.2.0 to < 7.2.8, or >= 7.4.0 to < 7.4.4
  3. Retrieve the installed FortiProxy version
    Run the CLI command: `get system status` on the FortiProxy device, or check via the web UI under Dashboard > Status.
    Affected if The version is >= 1.0.0 to < 7.0.17, >= 7.2.0 to < 7.2.10, or >= 7.4.0 to < 7.4.4
  4. Retrieve the installed FortiPAM version
    Run the CLI command: `get system status` on the FortiPAM device, or check via the web UI under System > Firmware or Dashboard.
    Affected if The version is >= 1.0.0 through 1.3.0 (inclusive)
  5. Retrieve the installed FortiSwitchManager version
    Run the CLI command: `get system status` on the FortiSwitchManager, or check via the management interface.
    Affected if The version is >= 7.0.1 to < 7.0.4 or >= 7.2.0 to < 7.2.4

The environment is affected if any FortiOS, FortiProxy, FortiPAM, or FortiSwitchManager instance matches the version ranges listed above; FortiWeb and FortiAuthenticator are affected but lack version specifics in this CVE record.

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.0.4 / 7.0.15 / 7.0.17 or later
Fixed in 7.0.47.0.157.0.17
Interim mitigation

Apply vendor-supplied patches from Fortinet for the specific affected product versions. For FortiOS/FortiProxy, upgrade to versions 7.4.4+, 7.2.8+, 7.0.15+, 6.4.16+, 6.2.17+, 6.0.19+. For FortiSwitchManager, upgrade to 7.2.4+ or 7.0.4+. For FortiPAM, upgrade to 1.2.1 or later.

Recommended fix High confidence

FortiOS 7.0.15/7.2.8/7.4.4 or later; FortiProxy 7.0.17/7.2.10/7.4.4 or later; FortiPAM 1.3.1 or later; FortiSwitchManager 7.0.4/7.2.4 or later

  1. 1. Identify the exact Fortinet product and version currently installed (FortiOS, FortiPAM, FortiProxy, or FortiSwitchManager)
  2. 2. Determine which product-specific fixed version applies: For FortiOS upgrade to 7.0.15+, 7.2.8+, or 7.4.4+; For FortiProxy upgrade to 7.0.17+, 7.2.10+, or 7.4.4+; For FortiPAM upgrade to 1.3.1 or higher; For FortiSwitchManager upgrade to 7.0.4+ or 7.2.4+
  3. 3. Review release notes for the target version to confirm the security fix is included
  4. 4. Schedule a maintenance window following standard change management procedures
  5. 5. Back up current configuration before upgrading
  6. 6. Perform the upgrade using Fortinet's recommended upgrade path (refer to FortiOS/Product Upgrade paths documentation)
  7. 7. After upgrade, verify the system is operational and the version is correct
  8. 8. Confirm the vulnerability is resolved by checking FortiGuard or system diagnostics
Caveat Upgrade between major versions (e.g., 6.x to 7.x) may require configuration changes; review Fortinet migration guides for major version upgrades

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

Fix this in Fortios Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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