Big Ip Access Policy ManagerApplication · F5
CVE-2025-54854
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 a BIG-IP APM OAuth access profile (Resource Server or Resource Client) is configured on a virtual server, undisclosed traffic can cause the apmd process to terminate. 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 denial of service vulnerability in F5 BIG-IP APM allows unauthenticated attackers to crash the apmd process by sending specifically crafted traffic to virtual servers configured with OAuth access profiles (Resource Server or Resource Client). The vulnerability has a CVSS base score of 7.5, indicating network-exploitable DoS with high availability impact.
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
Big Ip Access Policy ManagerApplication
>= 15.1.0, < 15.1.10.8>= 16.1.0, < 16.1.6.1>= 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Verify BIG-IP software versionRun `tmsh show sys version` or check in the web UI under System > Software Management > Image ListAffected if The version falls within these ranges: 15.1.0 to 15.1.10.7, 16.1.0 to 16.1.6.0, 17.1.0 to 17.1.2, or 17.5.0 to 17.5.1
-
Confirm APM module is provisionedRun `tmsh show sys provision apm` or check in the web UI under System > ProvisioningAffected if APM shows as provisioned (module status is not 'None' or 'Disabled')
-
Identify OAuth access profiles configured as Resource Server or Resource ClientRun `tmsh list apm profile oauth` or navigate to Access > Profiles / Policies > OAuth > Client / Server in the web UIAffected if Any OAuth profiles exist with type Resource Server or Resource Client configured
-
Check virtual servers using OAuth profilesRun `tmsh list ltm virtual one-vs` and inspect the access profile referenced, or check in the web UI under Local Traffic > Virtual Servers > Virtual Server ListAffected if Any virtual servers reference an OAuth access profile of type Resource Server or Resource Client
A system is affected if it runs a vulnerable BIG-IP version, has APM provisioned, and has virtual servers configured with OAuth Resource Server or Resource Client profiles.
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.
From vendor data15.1.10.816.1.6.117.1.3
Upgrade BIG-IP to a version that includes the fix for this vulnerability. Organizations should identify their current BIG-IP version, check against affected versions, and apply the appropriate security patch or update.
Fix this in Big Ip Access Policy Manager
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54854 — 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-54854 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