dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2025-58071

HIGH · 7.5 CVSS v3.1 Published 2025-10-15
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 IPsec is configured on the BIG-IP system, undisclosed traffic 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 · moderate confidence

This is a denial-of-service vulnerability in F5 BIG-IP systems where IPsec must be configured for the attack surface to exist. Undisclosed traffic can cause the Traffic Management Microkernel (TMM) to terminate, resulting in service disruption.

MitigationApply the F5 security patch when available. Until then, consider disabling IPsec if not required, or implement network filtering to block potential malicious IPsec traffic.

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.1>= 17.1.0, < 17.1.3= 17.5.0
Big Ip Advanced Firewall ManagerApplication
Affected:>= 15.1.0, < 15.1.10.8>= 16.1.0, < 16.1.6>= 17.1.0, < 17.1.3= 17.5.0
Big Ip Advanced Web Application FirewallApplication
Affected:>= 15.1.0, < 15.1.10.8>= 16.1.0, < 16.1.6.1>= 17.1.0, < 17.1.3= 17.5.0
Big Ip AnalyticsApplication
Affected:>= 15.1.0, < 15.1.10.8>= 16.1.0, < 16.1.6.1>= 17.1.0, < 17.1.3= 17.5.0
Big Ip Application Acceleration ManagerApplication
Affected:>= 15.1.0, < 15.1.10.8>= 16.1.0, < 16.1.6.1>= 17.1.0, < 17.1.3= 17.5.0
Big Ip Application Security ManagerApplication
Affected:>= 15.1.0, < 15.1.10.8>= 16.1.0, < 16.1.6.1>= 17.1.0, < 17.1.3= 17.5.0
Big Ip Application Visibility And ReportingApplication
Affected:>= 15.1.0, < 15.1.10.8>= 16.1.0, < 16.1.6.1>= 17.1.0, < 17.1.3= 17.5.0
Big Ip Automation ToolchainApplication
Affected:>= 15.1.0, < 15.1.10.8>= 16.1.0, < 16.1.6.1>= 17.1.0, < 17.1.3= 17.5.0

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. Identify installed BIG-IP version
    Run `tmsh show sys version` or check the web UI under Dashboard > General. Record the full version number including build.
    Affected if The version falls within these ranges: 15.1.0 to 15.1.10.8, 16.1.0 to 16.1.6.1, 17.1.0 to 17.1.3, or equals 17.5.0
  2. Confirm the BIG-IP product module
    Check which BIG-IP modules are licensed and running. In the web UI, go to System > License or run `tmsh show sys license` to list active modules.
    Affected if Any of these modules are present: APM, AFM, AWM, Analytics, AAM, ASM, AVR, or Automation Toolchain, and the version is in the affected range from step 1
  3. Verify IPsec configuration status
    Run `tmsh list net ipsec` or `tmsh show net ipsec` to list all IPsec policies and tunnels. Also check the web UI under Network > IPsec.
    Affected if Any IPsec tunnels, policies, or profiles are configured and active on the system
  4. Check for TMM crashes or restarts
    Review logs via `tmsh show sys crash` and check /var/log/ltm for TMM-related messages. Look for unexpected TMM process termination events.
    Affected if TMM crashes or unexpected restarts have occurred, especially after receiving IPsec traffic

The system is affected if it runs a vulnerable BIG-IP version AND has IPsec tunnels or policies configured, regardless of which BIG-IP module is in use.

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 / 16.1.6.1 or later
Fixed in 15.1.10.816.1.616.1.6.1
Interim mitigation

Apply the F5 security patch when available. Until then, consider disabling IPsec if not required, or implement network filtering to block potential malicious IPsec traffic.

Recommended fix High confidence

Upgrade to 15.1.10.8 (for 15.1.x), 16.1.6 or 16.1.6.1 (for 16.1.x), 17.1.3 (for 17.1.x), or a version higher than 17.5.0 (for 17.5.0)

  1. Identify the currently installed BIG-IP version using 'tmsh show sys version' or the web UI
Caveat Review F5 release notes for any configuration or compatibility changes before upgrading

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
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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