dbcve.org
Big Ip Advanced Firewall ManagerApplication · F5

CVE-2025-59478

HIGH · 7.5 CVSS v3.1 Published 2025-10-15
Fix available
A fix is available. Upgrade to 15.1.10.8 / 17.1.3 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 AFM denial-of-service (DoS) protection profile is configured on a virtual server, undisclosed requests can cause the Traffic Management Microkernel (TMM) 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 confidence

This is a denial-of-service vulnerability in F5 BIG-IP AFM (Advanced Firewall Module) where specific undisclosed requests sent to a virtual server configured with a DoS protection profile can cause the Traffic Management Microkernel (TMM) process to terminate, resulting in traffic disruption.

MitigationApply the F5 software update for this vulnerability. If immediate patching is not possible, consider removing the DoS protection profile from affected virtual servers or implementing network-level filtering as a temporary measure.

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 Advanced Firewall ManagerApplication
Affected:>= 15.1.0, < 15.1.10.8>= 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. Verify AFM module is provisioned
    Run `tmsh show sys provision` or check through BIG-IP GUI under System > Resource Provisioning to confirm Advanced Firewall Manager (AFM) is provisioned.
    Affected if AFM module is not provisioned on the BIG-IP device, the vulnerability does not apply.
  2. Check BIG-IP version against affected ranges
    Run `tmsh show sys version` or check the version through BIG-IP GUI under Dashboard. Compare the installed version to: 15.1.0 through 15.1.10.7, 17.1.0 through 17.1.2, or 17.5.0.
    Affected if Version falls within any of these ranges: >=15.1.0 and <15.1.10.8, >=17.1.0 and <17.1.3, or equals 17.5.0.
  3. Identify virtual servers with DoS protection profiles
    Run `tmsh list ltm virtual` and examine the `dos profile` or `security dos-profile` configuration for each virtual server. Alternatively, check through BIG-IP GUI under Local Traffic > Virtual Servers by viewing each virtual server's Security policy settings.
    Affected if A virtual server is configured with a DoS protection profile (either per-schedule or per虛擬伺服器 DoS profile) attached.
  4. Confirm virtual server is exposed to network
    Verify the virtual server has a destination IP and port configured and is in a enabled state by running `tmsh show ltm virtual` and checking for active listeners.
    Affected if The virtual server with the DoS protection profile is active and accepting traffic.

You are affected if AFM is provisioned, your BIG-IP version is in the affected ranges listed, AND you have an active virtual server configured with a DoS protection profile that can receive the specific malicious requests.

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

Apply the F5 software update for this vulnerability. If immediate patching is not possible, consider removing the DoS protection profile from affected virtual servers or implementing network-level filtering as a temporary measure.

Recommended fix High confidence

15.1.10.8 for 15.1.x line; 17.1.3 for 17.1.x line; 17.5.1+ for 17.5.0

  1. 1. Identify the current BIG-IP AFM version by running 'tmsh show sys version' or checking the web UI at System > Software > Image List
  2. 2. For BIG-IP 15.1.x versions (>=15.1.0, <15.1.10.8): Upgrade to version 15.1.10.8 or later
  3. 3. For BIG-IP 17.1.x versions (>=17.1.0, <17.1.3): Upgrade to version 17.1.3 or later
  4. 4. For BIG-IP 17.5.0: Upgrade to version 17.5.1 or later (the next available hotfix or stable release)
  5. 5. After upgrade, verify the TMM process stability by checking 'tmsh show sys tmm-info' and monitoring for any unexpected restarts
  6. 6. Test the DoS protection profile functionality to ensure the fix does not impact legitimate protection features
Caveat Review F5 release notes for any configuration or behavioral changes between current and target versions before upgrading

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

Fix this in Big Ip Advanced Firewall Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
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,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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