Big Ip Access Policy ManagerApplication · F5
CVE-2025-58424
A fix is available.
Upgrade to 15.1.10.8 / 16.1.6 or later.
See remediation →
62/100
Remediation priority · Elevated
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 · uneditedOn BIG-IP systems, undisclosed traffic can cause data corruption and unauthorized data modification in protocols which do not have message integrity protection. 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 · low confidenceDeveloping — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-07-31.
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
Big Ip Access Policy ManagerApplication
Affected:
>= 15.1.0, < 15.1.10.8>= 16.1.0, < 16.1.6>= 17.1.0, <= 17.1.2
Big Ip Advanced Firewall ManagerApplication
Affected:
>= 15.1.0, < 15.1.10.8>= 16.1.0, < 16.1.6>= 17.1.0, <= 17.1.2
Big Ip Advanced Web Application FirewallApplication
Affected:
>= 15.1.0, < 15.1.10.8>= 16.1.0, < 16.1.6>= 17.1.0, <= 17.1.2
Big Ip AnalyticsApplication
Affected:
>= 15.1.0, < 15.1.10.8>= 16.1.0, < 16.1.6>= 17.1.0, <= 17.1.2
Big Ip Application Acceleration ManagerApplication
Affected:
>= 15.1.0, < 15.1.10.8>= 16.1.0, < 16.1.6>= 17.1.0, <= 17.1.2
Big Ip Application Security ManagerApplication
Affected:
>= 15.1.0, < 15.1.10.8>= 16.1.0, < 16.1.6>= 17.1.0, <= 17.1.2
Big Ip Application Visibility And ReportingApplication
Affected:
>= 15.1.0, < 15.1.10.8>= 16.1.0, < 16.1.6>= 17.1.0, <= 17.1.2
Big Ip Automation ToolchainApplication
Affected:
>= 15.1.0, < 15.1.10.8>= 16.1.0, < 16.1.6>= 17.1.0, <= 17.1.2CVSS 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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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 15.1.10.8 / 16.1.6 or later
Fixed in
15.1.10.816.1.6
Recommended fix
High confidence
15.1.10.8+ (15.1.x branch), 16.1.6+ (16.1.x branch), or 17.1.3+ (17.1.x branch)
- 1. Identify the current BIG-IP version by running 'tmsh show sys version' or checking the web management console.
- 2. Based on your current major version (15.1.x, 16.1.x, or 17.1.x), plan upgrade to the fixed release: 15.1.10.8 or later, 16.1.6 or later, or 17.1.3 or later.
- 3. Review F5 BIG-IP upgrade guide at my.f5.com for pre-upgrade steps including backup of configuration (ucs file).
- 4. Download the appropriate hotfix or maintenance release from F5 downloads on my.f5.com.
- 5. Upload the ISO/image to the BIG-IP and install via tmsh: 'tmsh install sys software image <image-name> volume <volume-name>' or use the web UI.
- 6. Reboot the system into the new volume after installation completes.
- 7. Verify the upgrade was successful and the version matches the fixed release: 'tmsh show sys version'.
- 8. Test critical application functionality and verify the vulnerability is remediated.
Caveat Standard BIG-IP maintenance upgrade - review F5 release notes for any configuration or compatibility changes between versions
Generated from the published advisory — verify against the referenced sources before acting.
We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600.
Get the upgrade done
Scan for this in your stack
Free · runs locally
dbcve dependency scanner
Check whether your project pulls in CVE-2025-58424 — 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-2025-58424 in production — separate from our analysis above.
Know something about CVE-2025-58424?
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.
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