CVE-2026-24464
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 · uneditedWhen running in Appliance mode, a directory traversal vulnerability exists in an undisclosed iControl REST endpoint that may allow an authenticated attacker with administrator role privileges to cross a security boundary and delete files. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
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 · moderate confidenceA directory traversal vulnerability exists in an undisclosed iControl REST endpoint when running in Appliance mode, allowing authenticated administrators to delete files outside the intended directory. This affects F5 products in Appliance mode and requires valid admin credentials for exploitation.
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>= 16.1.0, <= 16.1.6= 21.0.0>= 17.1.0, <= 17.1.3>= 17.5.0, <= 17.5.1>= 16.1.0, <= 16.1.6= 21.0.0>= 17.1.0, <= 17.1.3>= 17.5.0, <= 17.5.1>= 16.1.0, <= 16.1.6= 21.0.0>= 17.1.0, <= 17.1.3>= 17.5.0, <= 17.5.1>= 16.1.0, <= 16.1.6= 21.0.0>= 17.1.0, <= 17.1.3>= 17.5.0, <= 17.5.1>= 16.1.0, <= 16.1.6= 21.0.0>= 17.1.0, <= 17.1.3>= 17.5.0, <= 17.5.1>= 16.1.0, <= 16.1.6= 21.0.0>= 17.1.0, <= 17.1.3>= 17.5.0, <= 17.5.1>= 16.1.0, <= 16.1.6= 21.0.0>= 17.1.0, <= 17.1.3>= 17.5.0, <= 17.5.1>= 16.1.0, <= 16.1.6= 21.0.0>= 17.1.0, <= 17.1.3>= 17.5.0, <= 17.5.1CVSS 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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:H/A:N
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 Big IP product moduleRun 'tmsh list sys module' or check the Big IP hostname/description which typically indicates the licensed module (APM, AFM, ASM, AVR, etc.)Affected if The system is running any of the following modules: Access Policy Manager, Advanced Firewall Manager, Advanced Web Application Firewall, Analytics, Application Acceleration Manager, Application Security Manager, Application Visibility And Reporting, or Automation Toolchain
-
Determine the Big IP versionRun 'tmsh show sys version' or check '/etc/product_version' fileAffected if The installed version matches any of these ranges: 16.1.0 through 16.1.6, exactly 21.0.0, 17.1.0 through 17.1.3, or 17.5.0 through 17.5.1
-
Verify if the system is running in Appliance modeRun 'tmsh list sys db provision.1hostmode' or check the 'sys global-settings' for appliance mode setting. Also check the output of 'tmsh show sys hardware' for appliance platform typeAffected if The system is configured in Appliance mode (single-node appliance mode, not cluster or standard standalone)
-
Confirm iControl REST endpoint is accessibleAttempt to reach the iControl REST API at https://localhost/mgmt or check that the REST daemon is running via 'tmsh show sys service restjavad'Affected if The iControl REST service is running and accessible to the administrator
The environment is affected if it is any F5 Big IP module (APM/AFM/ASM/etc.) within versions 16.1.0-16.1.6, 21.0.0, 17.1.0-17.1.3, or 17.5.0-17.5.1, running in Appliance mode with iControl REST enabled.
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 · scopedApply vendor-supplied patches for affected F5 products running in Appliance mode; restrict admin access and monitor iControl REST API activity for traversal patterns.
F5 has not published specific fixed versions in the available advisory; check my.f5.com for version-specific patches
- Check current Big IP version using 'tmsh show sys version' or the web UI
- Consult F5 my.f5.com for the specific hotfix or fixed version for CVE-2026-24464
- Apply the recommended hotfix or upgrade to a fixed version as specified by F5
- Verify the fix by confirming the version after remediation
- Test that the iControl REST endpoint no longer allows directory traversal
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2026-24464 — 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-2026-24464 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