dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2025-41433

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 a Session Initiation Protocol (SIP) message routing framework (MRF) application layer gateway (ALG) profile is configured on a Message Routing virtual server, undisclosed requests 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 is a F5 BIG-IP vulnerability where a specifically configured SIP MRF ALG profile on a Message Routing virtual server can be triggered by crafted requests to cause the TMM (Traffic Management Microkernel) to terminate, resulting in denial of service. The exact request format is undisclosed (likely for responsible disclosure).

MitigationApply the vendor patch when available. Until then, consider disabling the SIP MRF ALG profile on Message Routing virtual servers if not required, or implement rate limiting and traffic filtering on upstream devices 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. Check the installed BIG-IP version
    Run 'tmsh show /sys version' or view the version via the BIG-IP Configuration utility under System > Software Management > ISO Image
    Affected if version falls within 15.1.0-15.1.10, 16.1.0-16.1.4, or 17.1.0-17.1.1
  2. Identify SIP MRF ALG profiles configured on the system
    Run 'tmsh list /ltm sip mr-alg-profile all' to list all SIP MRF ALG profiles defined in the configuration
    Affected if any SIP MRF ALG profile exists in the configuration
  3. Identify Message Routing virtual servers
    Run 'tmsh list /ltm virtual all-properties' and examine the 'type' field for 'message-routing' or inspect the virtual server profile configuration for message routing settings
    Affected if any virtual server is configured with Message Routing type
  4. Verify if Message Routing virtual servers use SIP MRF ALG profiles
    For each Message Routing virtual server identified, run 'tmsh list /ltm virtual <name>' and check the 'profiles' section for sip-mr-alg-profile entry
    Affected if a Message Routing virtual server has a SIP MRF ALG profile assigned

You are affected if your BIG-IP version is in the affected range AND you have a Message Routing virtual server with a SIP MRF ALG profile configured.

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

Apply the vendor patch when available. Until then, consider disabling the SIP MRF ALG profile on Message Routing virtual servers if not required, or implement rate limiting and traffic filtering on upstream devices to reduce attack surface.

Recommended fix High confidence

Big IP 15.1.11+ (if supported), 16.1.5+, or 17.1.2+ depending on your current major version branch

  1. 1. Identify the currently installed Big IP version by running 'tmsh show sys version' or checking the web management console.
  2. 2. Determine which Big IP module (APM, AFM, ASM, etc.) has the SIP MRF ALG profile configured on Message Routing virtual servers.
  3. 3. For Big IP versions 15.1.x: Upgrade to version 15.1.11 or later.
  4. 4. For Big IP versions 16.1.x: Upgrade to version 16.1.5 or later.
  5. 5. For Big IP versions 17.1.x: Upgrade to version 17.1.2 or later.
  6. 6. After upgrade, verify the SIP MRF ALG profile configuration is functioning correctly.
  7. 7. Test that TMM no longer terminates upon receiving the previously problematic SIP requests.
Caveat Review F5 release notes for any compatibility changes between your current version and the target version; test in non-production environment first

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
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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