dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2025-58096

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.1 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 the database variable tm.tcpudptxchecksum is configured as non-default value Software-only on a 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

When the BIG-IP database variable tm.tcpudptxchecksum is set to non-default value 'Software-only', certain undisclosed network traffic can cause the Traffic Management Microkernel (TMM) to terminate, resulting in denial of service.

MitigationRevert tm.tcpudptxchecksum to its default value if currently configured as 'Software-only', or apply vendor-supplied patches when available.

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, <= 17.5.1
Big Ip Advanced Firewall 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, <= 17.5.1
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, <= 17.5.1
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, <= 17.5.1
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, <= 17.5.1
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, <= 17.5.1
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, <= 17.5.1
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, <= 17.5.1

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 `bigip_version` to retrieve the installed BIG-IP version
    Affected if The version falls within any of these ranges: >= 15.1.0 and < 15.1.10.8; >= 16.1.0 and < 16.1.6.1; >= 17.1.0 and < 17.1.3; >= 17.5.0 and <= 17.5.1
  2. Verify affected product module
    Confirm the system has any of the affected BIG-IP modules installed (APM, AFM, AWM, Analytics, AAM, ASM, AVR, or Automation Toolchain) by checking `tmsh show /sys module` or reviewing the licensed modules
    Affected if Any of the listed modules are licensed and running on an affected version
  3. Inspect tm.tcpudptxchecksum setting
    Run `tmsh list /sys db tm.tcpudptxchecksum` to view the current value of this database variable
    Affected if The value is set to 'Software-only' (non-default)
  4. Confirm default state
    If the tm.tcpudptxchecksum value is not explicitly set or shows the default hardware setting, the system is not vulnerable to this specific condition
    Affected if tm.tcpudptxchecksum is explicitly set to 'Software-only' AND the version is in the affected range

You are affected if your BIG-IP version is within the vulnerable ranges AND the tm.tcpudptxchecksum database variable is configured to 'Software-only'.

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.1 / 17.1.3 or later
Fixed in 15.1.10.816.1.6.117.1.3
Interim mitigation

Revert tm.tcpudptxchecksum to its default value if currently configured as 'Software-only', or apply vendor-supplied patches when available.

Recommended fix High confidence

Upgrade to 15.1.10.8 (for 15.1.x), 16.1.6.1 (for 16.1.x), 17.1.3 (for 17.1.x), or a version newer than 17.5.1 (for 17.5.x)

  1. 1. Identify the current BIG-IP version by running `tmsh show sys version` or checking the web UI.
  2. 2. Based on your current major version (15.1.x, 16.1.x, 17.1.x, or 17.5.x), plan upgrade to the fixed release: 15.1.10.8, 16.1.6.1, 17.1.3, or a version higher than 17.5.1.
  3. 3. Before upgrading, review F5 release notes for the target version to check for any compatibility notes or known issues.
  4. 4. Back up the BIG-IP configuration using `tmsh save sys config` or the web UI.
  5. 5. Perform the upgrade following F5 standard upgrade procedures (via ISO image or Hotfix).
  6. 6. After upgrade, verify the system boots correctly and TMM is running with `tmsh show sys tmm-info`.
  7. 7. Confirm the fix is applied by checking that the vulnerability is resolved in the new version.
Caveat Review F5 release notes for the target version for any potential compatibility or configuration 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
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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