dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2025-41414

HIGH · 7.5 CVSS v3.1 Published 2025-05-07
Fix available
A fix is available. Upgrade to 16.1.5 / 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 HTTP/2 client and server profile is configured on a virtual server, undisclosed requests can cause 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 where undisclosed HTTP/2 requests, when made against a virtual server configured with both HTTP/2 client and server profiles, can cause the TMM (Traffic Management Microkernel) to terminate, resulting in service disruption.

MitigationUntil a patch is available, consider disabling HTTP/2 profiles on affected virtual servers if not required, or implement iRule-based request filtering if the specific request pattern can be identified. Monitor for TMM crashes and consider rate limiting to reduce attack surface.

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.5>= 17.1.0, < 17.1.2
Big Ip Advanced Firewall ManagerApplication
Affected:>= 15.1.0, <= 15.1.10>= 16.1.0, < 16.1.5>= 17.1.0, < 17.1.2
Big Ip Advanced Web Application FirewallApplication
Affected:>= 15.1.0, <= 15.1.10>= 16.1.0, < 16.1.5>= 17.1.0, < 17.1.2
Big Ip AnalyticsApplication
Affected:>= 15.1.0, <= 15.1.10>= 16.1.0, < 16.1.5>= 17.1.0, < 17.1.2
Big Ip Application Acceleration ManagerApplication
Affected:>= 15.1.0, <= 15.1.10>= 16.1.0, < 16.1.5>= 17.1.0, < 17.1.2
Big Ip Application Security ManagerApplication
Affected:>= 15.1.0, <= 15.1.10>= 16.1.0, < 16.1.5>= 17.1.0, < 17.1.2
Big Ip Application Visibility And ReportingApplication
Affected:>= 15.1.0, <= 15.1.10>= 16.1.0, < 16.1.5>= 17.1.0, < 17.1.2
Big Ip Automation ToolchainApplication
Affected:>= 15.1.0, <= 15.1.10>= 16.1.0, < 16.1.5>= 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. Identify BIG-IP version
    Run `tmsh show sys version` or `bigstart version` to obtain the installed software version
    Affected if The installed version falls within 15.1.0-15.1.10, 16.1.0-16.1.4, or 17.1.0-17.1.1
  2. List virtual servers with HTTP/2 profiles
    Run `tmsh list ltm virtual one-line` and inspect the `http2` profile references for each virtual server
    Affected if Any virtual server references an HTTP/2 profile in its configuration
  3. Verify HTTP/2 client and server profile pairing
    Run `tmsh list ltm profile http2` to list all HTTP/2 profiles, then cross-reference with virtual server configurations to identify if both client and server HTTP/2 profiles are applied to the same virtual server
    Affected if A virtual server is configured with both an HTTP/2 client profile and an HTTP/2 server profile simultaneously
  4. Check for recent TMM crash events
    Run `tmsh show sys core` or review `/var/log/ltm` for TMM-related crash or termination messages
    Affected if TMM crashes or unexpected terminations have occurred recently without another known cause

You are affected if your BIG-IP version is within the affected ranges AND you have virtual servers configured with both HTTP/2 client and server 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.5 / 17.1.2 or later
Fixed in 16.1.517.1.2
Interim mitigation

Until a patch is available, consider disabling HTTP/2 profiles on affected virtual servers if not required, or implement iRule-based request filtering if the specific request pattern can be identified. Monitor for TMM crashes and consider rate limiting to reduce attack surface.

Recommended fix High confidence

Upgrade to BIG-IP 16.1.5 or later, or 17.1.2 or later. For 15.1.x deployments, migrate to a supported version branch (16.1.x or 17.1.x) as 15.1.x has reached end of support.

  1. 1. Verify the current BIG-IP version by running 'tmsh show sys version' or checking the web UI at System > Software > Image List
  2. 2. Identify all virtual servers using HTTP/2 client and server profiles via 'tmsh list ltm virtual profiles'
  3. 3. Schedule a maintenance window for the upgrade
  4. 4. Create a UCS backup before upgrading: 'tmsh save sys ucs <backup-name>'
  5. 5. Download the appropriate hotfix from F5 Downloads (my.f5.com): version 16.1.5 or later for 16.x line, version 17.1.2 or later for 17.x line
  6. 6. Upload the ISO image to the BIG-IP: 'tmsh install sys software add <image-name>'
  7. 7. Install the new volume: 'tmsh install sys software volume <volume-name> volume <new-volume>'
  8. 8. Reboot to activate the new version: 'tmsh reboot'
Caveat F5 recommends reviewing release notes for any configuration or behavioral changes between versions. Test in staging environment before production deployment.

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
  • 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-41414 — 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-41414 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