FortiswitchmanagerApplication · Fortinet
CVE-2024-26009
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 · uneditedAn authentication bypass using an alternate path or channel [CWE-288] vulnerability in Fortinet FortiOS 6.4.0 through 6.4.15, FortiOS 6.2.0 through 6.2.16, FortiOS 6.0 all versions, FortiPAM 1.2.0, FortiPAM 1.1.0 through 1.1.2, FortiPAM 1.0.0 through 1.0.3, FortiProxy 7.4.0 through 7.4.2, FortiProxy 7.2.0 through 7.2.8, FortiProxy 7.0.0 through 7.0.15, FortiSwitchManager 7.2.0 through 7.2.3, FortiSwitchManager 7.0.0 through 7.0.3 allows an unauthenticated attacker to seize control of a managed device via crafted FGFM requests, if the device is managed by a FortiManager, and if the attacker knows that FortiManager's serial number.
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 confidenceThis is an authentication bypass vulnerability (CWE-288) in FortiOS, FortiPAM, FortiProxy, and FortiSwitchManager that allows unauthenticated attackers to seize control of devices managed by FortiManager via crafted FGFM (FortiManager Firewall Management) requests. The attack requires the attacker to know the FortiManager's serial number, making it a targeted but high-severity vulnerability.
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
FortiswitchmanagerApplication
>= 7.0.0, < 7.0.4>= 7.2.0, < 7.2.4
FortiproxyApplication
>= 7.0.0, < 7.0.16>= 7.2.0, < 7.2.9>= 7.4.0, < 7.4.3
FortipamOperating system
>= 1.0.0, <= 1.2.0
FortiosOperating system
>= 6.0.0, < 6.2.17>= 6.4.0, < 6.4.16CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Fortinet productDetermine which Fortinet product is running in your environment: FortiOS (firewall), FortiProxy (proxy), FortiPAM (privilege access management), or FortiSwitchManager. Check the system information or product model.Affected if The product is FortiOS, FortiProxy, FortiPAM, or FortiSwitchManager within the affected version ranges.
-
Determine the product versionUse the product's CLI command 'get system status' or 'fw -c status' to retrieve the installed firmware version. Compare the version number against the affected ranges: FortiSwitchManager 7.0.0-7.0.3 or 7.2.0-7.2.3; FortiProxy 7.0.0-7.0.15, 7.2.0-7.2.8, or 7.4.0-7.4.2; FortiPAM 1.0.0-1.2.0; FortiOS 6.0.0-6.2.16 or 6.4.0-6.4.15.Affected if The installed version falls within any of these ranges.
-
Verify FGFM connectivity exposureCheck if the FGFM (FortiManager Firewall Management) port (typically port 541) is accessible from untrusted networks. Use network scanning or review firewall rules to determine if port 541/TCP is exposed to the internet or untrusted segments.Affected if FGFM ports are open to untrusted networks and the version is affected.
-
Assess FortiManager serial number exposureReview logs, configuration backups, support tickets, or public documentation for leakage of the FortiManager serial number. Check if the serial number appears in network traffic logs or is shared with third parties.Affected if The FortiManager serial number is discoverable by unauthenticated attackers and the product version is affected.
You are affected if you are running any of the affected FortiOS, FortiProxy, FortiPAM, or FortiSwitchManager versions AND your FGFM management interface is exposed to untrusted networks while the FortiManager serial number could be discovered by an attacker.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.2.176.4.167.0.4
Apply the vendor-supplied patches for affected versions. In the interim, restrict access to FortiManager serial number information and limit FGFM traffic between untrusted networks and managed devices.
Upgrade to FortiOS 6.2.17+/6.4.16+, FortiProxy 7.0.16+/7.2.9+/7.4.3+, FortiSwitchManager 7.0.4+/7.2.4+, or latest FortiPAM version from Fortinet
- Identify the exact version of Fortinet product currently installed (FortiOS, FortiProxy, FortiSwitchManager, or FortiPAM)
- For FortiOS 6.0.x: Upgrade to version 6.2.17 or later, or 6.4.16 or later (6.0.x is end-of-life; migrate to 6.2.17+/6.4.16+ or preferably 7.x)
- For FortiOS 6.2.x: Upgrade to version 6.2.17 or later
- For FortiOS 6.4.x: Upgrade to version 6.4.16 or later
- For FortiProxy 7.0.x: Upgrade to version 7.0.16 or later
- For FortiProxy 7.2.x: Upgrade to version 7.2.9 or later
- For FortiProxy 7.4.x: Upgrade to version 7.4.3 or later
- For FortiSwitchManager 7.0.x: Upgrade to version 7.0.4 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortiswitchmanager
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-26009 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-26009 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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