dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2025-20058

HIGH · 7.5 CVSS v3.1 Published 2025-02-05
Fix available
A fix is available. Upgrade to 16.1.6 / 17.1.2 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 message routing profile is configured on a virtual server, undisclosed traffic can cause an increase in memory resource utilization. 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 confidence

A denial-of-service vulnerability in F5 BIG-IP allows undisclosed traffic patterns directed at virtual servers with message routing profiles enabled to cause excessive memory consumption, potentially leading to resource exhaustion and service disruption.

MitigationApply the F5 hotfix for CVE-2025-20058 when released, or temporarily disable the message routing profile on affected virtual servers if the feature is not actively required.

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>= 16.1.0, < 16.1.6>= 17.1.0, < 17.1.2
Big Ip Advanced Firewall ManagerApplication
Affected:>= 15.1.0, <= 15.1.10>= 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>= 16.1.0, < 16.1.6>= 17.1.0, < 17.1.2
Big Ip AnalyticsApplication
Affected:>= 15.1.0, <= 15.1.10>= 16.1.0, < 16.1.6>= 17.1.0, < 17.1.2
Big Ip Application Acceleration ManagerApplication
Affected:>= 15.1.0, <= 15.1.10>= 16.1.0, < 16.1.6>= 17.1.0, < 17.1.2
Big Ip Application Security ManagerApplication
Affected:>= 15.1.0, <= 15.1.10>= 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>= 16.1.0, < 16.1.6>= 17.1.0, < 17.1.2
Big Ip Automation ToolchainApplication
Affected:>= 15.1.0, <= 15.1.10>= 16.1.0, < 16.1.6>= 17.1.0, < 17.1.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 view the BIG-IP version in the web UI under System > Software > Image
    Affected if Version is 15.1.0-15.1.10, 16.1.0-16.1.5, or 17.1.0-17.1.1
  2. Verify message routing profile configuration
    Run 'tmsh list ltm virtual all profile' to list virtual servers and their assigned profiles, or inspect virtual server settings in the web UI under Local Traffic > Virtual Servers
    Affected if Any virtual server has a message routing profile (such as mqtt, amqp, or similar messaging protocol profiles) assigned
  3. Identify active message routing profiles
    Run 'tmsh list ltm profile message-routing all' to see all message routing profiles configured on the system
    Affected if Any message routing profiles exist and are associated with virtual servers
  4. Check virtual server profile assignments
    Run 'tmsh show ltm virtual' and review the profile section for each virtual server, or use the web UI to audit virtual server configurations for message routing profile bindings
    Affected if Virtual servers are using message routing profiles in the affected version range

You are affected if your BIG-IP runs version 15.1.0-15.1.10, 16.1.0-16.1.5, or 17.1.0-17.1.1 AND has any virtual servers with message routing profiles enabled.

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 16.1.6 / 17.1.2 or later
Fixed in 16.1.617.1.2
Interim mitigation

Apply the F5 hotfix for CVE-2025-20058 when released, or temporarily disable the message routing profile on affected virtual servers if the feature is not actively required.

Recommended fix High confidence

16.1.6 or later for 16.1.x line; 17.1.2 or later for 17.1.x line; 15.1.11 or later for 15.1.x line

  1. 1. Identify the current BIG-IP version by running 'tmsh show sys version' or checking the web UI status page
  2. 2. Determine which version line (15.1.x, 16.1.x, or 17.1.x) is currently deployed
  3. 3. For version 15.1.0-15.1.10: Upgrade to 15.1.11 or the latest 15.1.x maintenance release
  4. 4. For version 16.1.0-16.1.5: Upgrade to 16.1.6 or the latest 16.1.x maintenance release
  5. 5. For version 17.1.0-17.1.1: Upgrade to 17.1.2 or the latest 17.1.x maintenance release
  6. 6. Download the appropriate hotfix from F5 Downloads (my.f5.com)
  7. 7. Review F5 release notes for any prerequisites or migration considerations
  8. 8. Perform the upgrade following F5 standard upgrade procedures, preferably in a test environment first
Caveat Standard F5 upgrade risks apply - review compatibility notes and test in non-production environment before deploying to production

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
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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