dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2025-52585

HIGH · 7.5 CVSS v3.1 Published 2025-08-13
Fix available
A fix is available. Upgrade to 15.1.10.8 / 16.1.6 or later.
See remediation →
84/100
Remediation priority · High
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
When a BIG-IP LTM Client SSL profile is configured on a virtual server with SSL Forward Proxy enabled and Anonymous Diffie-Hellman (ADH) ciphers enabled, undisclosed requests can cause the Traffic Management Microkernel (TMM) 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 · high confidence

This vulnerability allows an attacker to cause a denial of service on F5 BIG-IP LTM devices by sending specially crafted SSL requests to virtual servers that have both SSL Forward Proxy enabled and Anonymous Diffie-Hellman (ADH) ciphers configured in their Client SSL profile. The attack triggers a TMM (Traffic Management Microkernel) termination, disrupting traffic processing.

MitigationDisable Anonymous Diffie-Hellman (ADH) ciphers in Client SSL profiles that have SSL Forward Proxy enabled, or disable SSL Forward Proxy if ADH ciphers are required for compatibility.

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
Affected:>= 15.1.0, < 15.1.10.8>= 16.1.0, < 16.1.6>= 17.1.0, < 17.1.2.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.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.2
Big Ip AnalyticsApplication
Affected:>= 15.1.0, < 15.1.10.8>= 16.1.0, < 16.1.6>= 17.1.0, < 17.1.2.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.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.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.2
Big Ip Automation ToolchainApplication
Affected:>= 15.1.0, < 15.1.10.8>= 16.1.0, < 16.1.6>= 17.1.0, < 17.1.2.2

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Check BIG-IP version
    Run 'tmsh show sys version' or 'bigpipe version' to obtain the installed version number
    Affected if The installed version falls within >= 15.1.0 < 15.1.10.8, >= 16.1.0 < 16.1.6, or >= 17.1.0 < 17.1.2.2
  2. Identify SSL Forward Proxy enabled profiles
    Run 'tmsh list ltm profile client-ssl all-properties' and search for 'ssl forward-proxy enabled'
    Affected if Any Client SSL profile has SSL Forward Proxy set to enabled
  3. Check for ADH ciphers in Client SSL profiles
    Run 'tmsh list ltm profile client-ssl all-properties' and examine the 'ciphers' or 'cipher-group' setting for ADH or anon DH cipher strings such as 'ADH'
    Affected if Any Client SSL profile (particularly those with SSL Forward Proxy enabled) includes ADH or Anonymous Diffie-Hellman ciphers in its cipher configuration
  4. Identify virtual servers using affected profiles
    Run 'tmsh list ltm virtual all-properties' and cross-reference with the SSL Forward Proxy enabled profiles that contain ADH ciphers
    Affected if Any virtual server references a Client SSL profile that has both SSL Forward Proxy enabled and ADH ciphers configured

A user is affected if their BIG-IP version is within the vulnerable ranges AND they have virtual servers using Client SSL profiles with SSL Forward Proxy enabled and ADH ciphers configured, as this combination triggers TMM termination when specially crafted SSL requests are sent.

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 15.1.10.8 / 16.1.6 / 17.1.2.2 or later
Fixed in 15.1.10.816.1.617.1.2.2
Interim mitigation

Disable Anonymous Diffie-Hellman (ADH) ciphers in Client SSL profiles that have SSL Forward Proxy enabled, or disable SSL Forward Proxy if ADH ciphers are required for compatibility.

Recommended fix High confidence

Upgrade to BIG-IP 15.1.10.8, 16.1.6, or 17.1.2.2 (or later) depending on your current major version branch

  1. Identify the currently running BIG-IP version using 'tmsh show sys version' or the web management console.
  2. Confirm the affected module (LTM with Client SSL profile) is in use with SSL Forward Proxy enabled.
  3. Access the F5 Downloads portal at my.f5.com and download the hotfix corresponding to your version branch: 15.1.10.8, 16.1.6, or 17.1.2.2.
  4. Upload the ISO/image to the BIG-IP via the web interface (System > Software Management > Image List) or via tmsh: 'tmsh install sys software volume <volume_name> file <image_name>'.
  5. Create a new volume and install the software image, then boot the BIG-IP to the new volume from 'System > Software Management > Boot Location' or via tmsh: 'tmsh boot system volume <new_volume_name>'.
  6. After upgrade, verify the fix by confirming the version matches one of the fixed releases: 15.1.10.8, 16.1.6, or 17.1.2.2.
  7. Alternatively, as a config mitigation, navigate to the Client SSL profile (Local Traffic > Profiles > SSL > Client) and remove any Anonymous Diffie-Hellman (ADH) ciphers from the cipher list, or disable SSL Forward Proxy if ADH ciphers are not required.
Caveat Review F5 release notes for the target version for any compatibility notes; hotfix upgrades are generally safe but test in non-production environment first

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

Fix this in Big Ip Access Policy Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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