dbcve.org
Big Ip Application Security ManagerApplication · F5

CVE-2025-55669

HIGH · 7.5 CVSS v3.1 Published 2025-10-15
Fix available
A fix is available. Upgrade to 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 the BIG-IP Advanced WAF and ASM security policy and a server-side HTTP/2 profile are configured on a virtual server, 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 F5 BIG-IP vulnerability requires both the Advanced WAF or ASM security policy AND a server-side HTTP/2 profile to be configured on a virtual server. When the TMM processes specific undisclosed traffic patterns, it causes the Traffic Management Microkernel to terminate, resulting in denial of service for affected virtual servers.

MitigationApply the F5 patch when available. Alternatively, consider disabling the server-side HTTP/2 profile on affected virtual servers if not required for business operations, or implement additional rate limiting and monitoring as a temporary workaround until patching is possible.

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 Application Security ManagerApplication
Affected:>= 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 ASM or Advanced WAF policy assignment on virtual servers
    Run 'tmsh list ltm virtual one-line' or inspect virtual server configurations in the web UI under Local Traffic > Virtual Servers. Look for 'security-policy' or 'asm-policy' in the virtual server configuration.
    Affected if Any virtual server has an ASM or Advanced WAF security policy assigned
  2. Check for server-side HTTP/2 profile on virtual servers
    Run 'tmsh list ltm virtual all-properties' and search for 'http2' in the profile configuration, or inspect virtual servers in the web UI under Traffic Management > Virtual Servers > Profiles. Verify if an HTTP/2 profile is assigned in the server-side profile settings.
    Affected if Any virtual server has a server-side HTTP/2 profile configured
  3. Confirm the affected ASM/Advanced WAF version
    Run 'tmsh show /sys version' or check the version displayed in the web UI under iControl > System > Software Management. Compare the installed version against the affected ranges: 16.1.0 to 16.1.5 (less than 16.1.6) or 17.1.0 to 17.1.2.
    Affected if The installed ASM or Advanced WAF version falls within 16.1.0 to 16.1.5 or 17.1.0 to 17.1.2

A virtual server is vulnerable only if it has both an ASM/Advanced WAF security policy AND a server-side HTTP/2 profile configured, AND the ASM version is within the affected ranges.

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

Apply the F5 patch when available. Alternatively, consider disabling the server-side HTTP/2 profile on affected virtual servers if not required for business operations, or implement additional rate limiting and monitoring as a temporary workaround until patching is possible.

Recommended fix High confidence

Upgrade to BIG-IP ASM 16.1.6 or later (for 16.x line); upgrade to 17.1.3 or later (for 17.x line)

  1. 1. Identify the current BIG-IP ASM version by running 'tmsh show sys version' or checking the web UI.
  2. 2. For BIG-IP 16.1.x versions: Plan upgrade to version 16.1.6 or later.
  3. 3. For BIG-IP 17.1.x versions: Plan upgrade to version 17.1.3 or later.
  4. 4. Before upgrading, back up the BIG-IP configuration using 'tmsh save sys config' and create a UCS archive with 'tmsh save sys ucs [filename]'.
  5. 5. Review F5 upgrade documentation and ensure the target version is compatible with your hardware/platform.
  6. 6. Perform the upgrade following F5 standard upgrade procedures - typically via web UI (System > Software Management > ISO Image) or via tmsh.
  7. 7. After upgrade, verify the ASM security policy and HTTP/2 profile are functioning correctly.
  8. 8. Monitor TMM processes to confirm stability and no unexpected terminations occur.
Caveat Standard F5 upgrade risks apply - test in non-production environment first; review F5 release notes for any configuration or behavior changes between versions

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

Fix this in Big Ip Application Security Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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