dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2025-41431

HIGH · 7.5 CVSS v3.1 Published 2025-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 connection mirroring is configured on a virtual server, undisclosed requests can cause the Traffic Management Microkernel (TMM) to terminate in the standby BIG-IP systems in a traffic group. 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. When connection mirroring is configured on a virtual server, the TMM (Traffic Management Microkernel) can be forced to terminate on standby BIG-IP systems within a traffic group when processing undisclosed requests. This causes failover disruption and service unavailability.

MitigationApply the applicable F5 software update when available. Until then, consider disabling connection mirroring on virtual servers if not required, or restrict administrative access 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:= 17.1.2
Big Ip Advanced Firewall ManagerApplication
Affected:= 17.1.2
Big Ip AnalyticsApplication
Affected:= 17.1.2
Big Ip Application Acceleration ManagerApplication
Affected:= 17.1.2
Big Ip Application Security ManagerApplication
Affected:= 17.1.2
Big Ip Domain Name SystemApplication
Affected:= 17.1.2
Big Ip Fraud Protection ServiceApplication
Affected:= 17.1.2
Big Ip Global Traffic ManagerApplication
Affected:= 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 the installed BIG-IP version
    Run 'tmsh show sys version' or check the BIG-IP GUI under Dashboard > System Information > Version to determine the exact software version
    Affected if The installed version is exactly 17.1.2 (this specific version is affected; other versions may not be)
  2. List virtual servers with connection mirroring enabled
    Use 'tmsh list ltm virtual' to view virtual server configurations. Look for 'mirror' or 'connection-mirror' settings within each virtual server definition
    Affected if Any virtual server has connection mirroring (connection-mirror) explicitly enabled in its configuration
  3. Check device group and traffic group membership
    Run 'tmsh show cm device-group' and 'tmsh show ltm traffic-group' to identify if the BIG-IP device is part of a device group and assigned to a traffic group
    Affected if The device is part of a device group with multiple devices and is assigned to an active or standby traffic group (the flaw affects standby units)
  4. Verify high availability status
    Check the failover state using 'tmsh show cm failover-status' or review the GUI Device Trust and Failover status to confirm a standby or active-standby configuration exists
    Affected if The system has a standby peer in its traffic group (the vulnerability triggers on standby systems during specific request processing)

You are affected if running version 17.1.2 AND have connection mirroring enabled on any virtual server AND your device is part of a traffic group with a standby peer, as all three conditions must be present for the flaw to be exploitable.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the applicable F5 software update when available. Until then, consider disabling connection mirroring on virtual servers if not required, or restrict administrative access to reduce attack surface.

Fix this in Big Ip Access Policy Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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