dbcve.org
Big Ip Next Service Proxy For KubernetesApplication · F5

CVE-2025-22846

HIGH · 7.5 CVSS v3.1 Published 2025-02-05
Fix available
A fix is available. Upgrade to 1.7.7 / 15.1.10.6.0.11.6-ENG 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 SIP Session and Router ALG profiles are configured on a Message Routing type 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 is a denial of service vulnerability in F5 BIG-IP/BIG-IQ systems. When SIP Session and Router ALG (Application Layer Gateway) profiles are configured on a Message Routing type virtual server, specific undisclosed traffic patterns can cause the Traffic Management Microkernel (TMM) to terminate, resulting in service disruption.

MitigationIf SIP ALG functionality is not required, remove or disable the SIP Session and Router ALG profiles from affected Message Routing virtual servers. Otherwise, apply vendor-supplied patches when available.

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 Next Service Proxy For KubernetesApplication
Affected:>= 1.7.0, < 1.7.7= 1.8.0= 1.8.1= 1.8.2= 1.9.0
Big Ip Access Policy ManagerApplication
Affected:>= 15.1.0, < 15.1.10.6.0.11.6>= 16.1.0, < 16.1.5>= 17.1.0, < 17.1.2
Big Ip Advanced Firewall ManagerApplication
Affected:>= 15.1.0, < 15.1.10.6.0.11.6-ENG>= 16.1.0, < 16.1.5>= 17.1.0, < 17.1.2
Big Ip AnalyticsApplication
Affected:>= 15.1.0, < 15.1.10.6.0.11.6>= 16.1.0, < 16.1.5>= 17.1.0, < 17.1.2
Big Ip Application Acceleration ManagerApplication
Affected:>= 15.1.0, < 15.1.10.6.0.11.6>= 16.1.0, < 16.1.5>= 17.1.0, < 17.1.2
Big Ip Application Security ManagerApplication
Affected:>= 15.1.0, < 15.1.10.6.0.11.6>= 16.1.0, < 16.1.5>= 17.1.0, < 17.1.2
Big Ip Domain Name SystemApplication
Affected:>= 15.1.0, < 15.1.10.6.0.11.6>= 16.1.0, < 16.1.5>= 17.1.0, < 17.1.2
Big Ip Fraud Protection ServiceApplication
Affected:>= 15.1.0, < 15.1.10.6.0.11.6>= 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 F5 product and version
    Run 'tmsh show sys version' or check the F5 management console for the installed BIG-IP/BIG-IQ version
    Affected if Version falls within any of the affected ranges listed for the product
  2. Locate Message Routing virtual servers
    Run 'tmsh list ltm virtual where type equals message-routing' or use F5 configuration utility to list virtual servers of type 'Message Routing'
    Affected if Any virtual server is configured with Message Routing type
  3. Check for SIP Session ALG profile attachment
    Run 'tmsh list ltm virtual <virtual-name>' and inspect the 'security-nat-policy' or 'alg-phase' settings, or check via F5 GUI under the virtual server properties for attached ALG profiles
    Affected if A Message Routing virtual server has a SIP Session ALG profile attached
  4. Check for SIP Router ALG profile attachment
    Run 'tmsh list ltm virtual <virtual-name>' and inspect the 'alg' or 'sip-router-alg' settings, or check via F5 GUI under the virtual server properties for attached SIP Router ALG profiles
    Affected if A Message Routing virtual server has a SIP Router ALG profile attached

User is affected if their F5 product version is within the listed vulnerable ranges AND they have Message Routing virtual servers with SIP Session or Router ALG profiles actively 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 1.7.7 / 15.1.10.6.0.11.6-ENG / 15.1.10.6.0.11.6 or later
Fixed in 1.7.715.1.10.6.0.11.6-ENG15.1.10.6.0.11.6
Interim mitigation

If SIP ALG functionality is not required, remove or disable the SIP Session and Router ALG profiles from affected Message Routing virtual servers. Otherwise, apply vendor-supplied patches when available.

Recommended fix High confidence

Upgrade to Big-IP 15.1.10.6.0.11.6 or later (15.1.x), 16.1.5 or later (16.1.x), 17.1.2 or later (17.1.x); for Big-IP Next SPK upgrade to 1.7.7+ or 1.8.3+

  1. 1. Identify the currently installed Big-IP version by checking the system information or using 'tmsh show sys version' command.
  2. 2. For Big IP Next Service Proxy For Kubernetes: upgrade to version 1.7.7 or later (for 1.8.x versions, upgrade to 1.8.3 or later).
  3. 3. For Big IP Access Policy Manager, Advanced Firewall Manager, Analytics, Application Acceleration Manager, Application Security Manager, Domain Name System, and Fraud Protection Service: upgrade to version 15.1.10.6.0.11.6 or later for 15.1.x; upgrade to version 16.1.5 or later for 16.1.x; upgrade to version 17.1.2 or later for 17.1.x.
  4. 4. After upgrading, verify the SIP Session and Router ALG profile configurations on Message Routing virtual servers are still functioning as expected.
  5. 5. Test that TMM remains stable and does not terminate under normal traffic conditions.
Caveat Review F5 release notes for any configuration or behavioral changes between versions before upgrading

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

Fix this in Big Ip Next Service Proxy For Kubernetes Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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