dbcve.org
FortiosOperating system · Fortinet

CVE-2024-26011

CRITICAL · 9.8 CVSS v3.1 Published 2024-11-12
Fix available
A fix is available. Upgrade to 1.3.0 / 6.0.15 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 missing authentication for critical function in Fortinet FortiManager version 7.4.0 through 7.4.2, 7.2.0 through 7.2.4, 7.0.0 through 7.0.11, 6.4.0 through 6.4.14, FortiPAM version 1.2.0, 1.1.0 through 1.1.2, 1.0.0 through 1.0.3, FortiProxy version 7.4.0 through 7.4.2, 7.2.0 through 7.2.9, 7.0.0 through 7.0.17, 2.0.0 through 2.0.14, 1.2.0 through 1.2.13, 1.1.0 through 1.1.6, 1.0.0 through 1.0.7, FortiSwitchManager version 7.2.0 through 7.2.3, 7.0.0 through 7.0.3, FortiPortal version 6.0.0 through 6.0.14, 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 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

Missing authentication vulnerability in FortiManager, FortiPAM, FortiProxy, FortiSwitchManager, FortiPortal, and FortiOS allows unauthenticated attackers to execute arbitrary code or commands by sending specially crafted packets to the affected system. This is a critical authentication bypass that enables remote code execution without any credentials.

MitigationApply Fortinet's available security patches for the affected versions. If immediate patching is not feasible, restrict network access to management interfaces using firewalls or VPNs and monitor for anomalous packets targeting these services.

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
FortimanagerApplication
Affected:>= 6.4.0, < 6.4.15>= 7.0.0, < 7.0.12>= 7.2.0, < 7.2.5>= 7.4.0, < 7.4.3
FortiswitchmanagerApplication
Affected:>= 7.0.0, < 7.0.4>= 7.2.0, < 7.2.4
FortiportalApplication
Affected:>= 5.3.0, < 6.0.15

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

CVSS:3.1/AV:N/AC:L/PR:N/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 Fortinet product and version
    Run `get system status` via CLI or check the WebUI dashboard for the firmware version. Common paths: FortiOS/FortiProxy: CLI `get system status` or WebUI Dashboard > Status. FortiManager: CLI `get system status` or System Settings > Dashboard. FortiPAM: CLI `get system status`. FortiPortal: check About page in GUI or `get system status` CLI. FortiSwitchManager: check in FortiManager or local CLI.
    Affected if The product is one of FortiOS, FortiProxy, FortiManager, FortiPAM, FortiSwitchManager, or FortiPortal and the version falls within any of the affected ranges: FortiOS 6.0.0-7.0.14, 7.2.0-7.2.7, 7.4.0-7.4.3; FortiProxy 1.0.0-7.0.16, 7.2.0-7.2.9, 7.4.0-7.4.3; FortiManager 6.4.0-6.4.14, 7.0.0-7.0.11, 7
  2. Determine if management interface is network-exposed
    Review firewall rules and interface bindings. In FortiOS/FortiProxy: run `get system interface` or check WebUI Network > Interfaces. Look for management interfaces (port1, mgmt, etc.) with administrative access enabled and verify whether they are bound to external/untrusted zones or have global access (set administrative-access `https` or `http` on WAN-facing interfaces).
    Affected if The management interface (GUI, CLI, or REST API) is reachable from untrusted networks or the internet without VPN or IP restriction, enabling unauthenticated attackers to send packets directly to the system.
  3. Check for anomalous authentication attempts or exploitation indicators
    Review logs for failed authentication from unusual sources or successful authentication without corresponding login events. Run: `execute log filter category 1` then `execute log display` for event logs. Search for: source IPs outside your admin range, multiple failed attempts followed by a successful unauthenticated session, or JSON/API calls to `/api/v2/` endpoints without valid tokens.
    Affected if Logs show successful administrative actions or API calls from unknown IPs without prior authentication events, or patterns of mass authentication failures followed by suspicious command execution.

A system is affected if it runs any of the listed Fortinet products within the specified version ranges AND has its management interface accessible from network segments where untrusted actors could send packets directly to the system.

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.3.0 / 6.0.15 / 6.4.15 or later
Fixed in 1.3.06.0.156.4.15
Interim mitigation

Apply Fortinet's available security patches for the affected versions. If immediate patching is not feasible, restrict network access to management interfaces using firewalls or VPNs and monitor for anomalous packets targeting these services.

Recommended fix High confidence

Upgrade to the latest version in your current release branch: FortiOS 7.0.15+/7.2.8+/7.4.4+, FortiPAM 1.3.0+, FortiProxy 7.0.17+/7.2.10+/7.4.4+, FortiManager 6.4.15+/7.0.12+/7.2.5+/7.4.3+, FortiSwitchManager 7.0.4+/7.2.4+, FortiPortal 6.0.15+

  1. 1. Identify the Fortinet product(s) in your environment from the affected product list (FortiOS, FortiPAM, FortiProxy, FortiManager, FortiSwitchManager, FortiPortal)
  2. 2. Determine the currently installed version for each affected device using the web UI or CLI command: get system status
  3. 3. For FortiOS: upgrade to 7.0.15, 7.2.8, or 7.4.4 (or higher) depending on your branch
  4. 4. For FortiPAM: upgrade to 1.3.0 or higher
  5. 5. For FortiProxy: upgrade to 7.0.17, 7.2.10, or 7.4.4 (or higher) depending on your branch
  6. 6. For FortiManager: upgrade to 6.4.15, 7.0.12, 7.2.5, or 7.4.3 (or higher) depending on your branch
  7. 7. For FortiSwitchManager: upgrade to 7.0.4 or 7.2.4 (or higher) depending on your branch
  8. 8. For FortiPortal: upgrade to 6.0.15 or higher
Caveat Major version upgrades may require configuration migration testing; review Fortinet upgrade guides for your product branch before proceeding

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

Fix this in Fortios Scoped from the published advisory
  • Consultation12.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA6.0 h
54.0 hours of engineering $9,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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