dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2025-41399

HIGH · 7.5 CVSS v3.1 Published 2025-05-07
Fix available
A fix is available. Upgrade to 15.1.9 / 16.1.4 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 Stream Control Transmission Protocol (SCTP) profile is configured on a virtual server, undisclosed requests can cause an increase in memory resource utilization. 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

A vulnerability in the SCTP profile handling of virtual servers allows remote attackers to cause excessive memory consumption through undisclosed requests, potentially leading to denial of service. The memory exhaustion occurs due to improper handling of SCTP traffic patterns.

MitigationIf SCTP functionality is not required, remove the SCTP profile from affected virtual servers. Monitor memory utilization and apply vendor patches when available. Consider implementing rate limiting on SCTP-enabled virtual servers as a temporary mitigation.

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.9>= 16.1.0, < 16.1.4= 17.1.0
Big Ip Advanced Firewall ManagerApplication
Affected:>= 15.1.0, < 15.1.9>= 16.1.0, < 16.1.4= 17.1.0
Big Ip Advanced Web Application FirewallApplication
Affected:>= 15.1.0, < 15.1.9>= 16.1.0, < 16.1.4= 17.1.0
Big Ip AnalyticsApplication
Affected:>= 15.1.0, < 15.1.9>= 16.1.0, < 16.1.4= 17.1.0
Big Ip Application Acceleration ManagerApplication
Affected:>= 15.1.0, < 15.1.9>= 16.1.0, < 16.1.4= 17.1.0
Big Ip Application Security ManagerApplication
Affected:>= 15.1.0, < 15.1.9>= 16.1.0, < 16.1.4= 17.1.0
Big Ip Application Visibility And ReportingApplication
Affected:>= 15.1.0, < 15.1.9>= 16.1.0, < 16.1.4= 17.1.0
Big Ip Automation ToolchainApplication
Affected:>= 15.1.0, < 15.1.9>= 16.1.0, < 16.1.4= 17.1.0

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 check the BIG-IP version through the web UI (System > Software Management > ISO Image) or 'bigpipe version' command
    Affected if The installed version falls within >= 15.1.0, < 15.1.9 OR >= 16.1.0, < 16.1.4 OR = 17.1.0
  2. Identify SCTP profiles configured on the system
    Run 'tmsh list ltm profile sctp all' to list all SCTP profiles defined on the Big IP device
    Affected if Any SCTP profiles exist in the configuration
  3. Check which virtual servers use SCTP profiles
    Run 'tmsh list ltm virtual all' and examine the 'profile sctp' or 'profile' section of each virtual server definition
    Affected if Any virtual server has an SCTP profile assigned to it
  4. Verify SCTP protocol handling is enabled on virtual servers
    Review the virtual server configuration with 'tmsh show ltm virtual <virtual_name>' and look for SCTP-related profile references
    Affected if SCTP profile is explicitly assigned to a virtual server

The environment is affected only if the Big IP version is within the affected ranges AND SCTP profiles are assigned to virtual servers, enabling the vulnerable SCTP traffic handling code path.

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 15.1.9 / 16.1.4 or later
Fixed in 15.1.916.1.4
Interim mitigation

If SCTP functionality is not required, remove the SCTP profile from affected virtual servers. Monitor memory utilization and apply vendor patches when available. Consider implementing rate limiting on SCTP-enabled virtual servers as a temporary mitigation.

Recommended fix High confidence

Upgrade to 15.1.9 or later (if on 15.1.x); Upgrade to 16.1.4 or later (if on 16.1.x); Upgrade to 17.1.1 or later (if on 17.1.0)

  1. 1. Identify the currently installed Big IP version using 'tmsh show sys version' or the web management console
  2. 2. Determine which Big IP modules (APM, AFM, ASM, etc.) are in use and note their configurations
  3. 3. Check if any virtual servers have an SCTP profile configured by reviewing virtual server settings in the web UI or via 'tmsh list ltm virtual <name> profile'
  4. 4. Schedule a maintenance window for the upgrade process
  5. 5. Back up the current configuration using 'tmsh save sys config' or the web UI backup function
  6. 6. Download the appropriate fixed version from F5 downloads (15.1.9+, 16.1.4+, or 17.1.1+)
  7. 7. Upload the ISO image to the Big IP device
  8. 8. Install the upgrade using 'tmsh install sys software' or the web UI software installation wizard
Caveat Major version upgrades (e.g., 15.x to 16.x or 16.x to 17.x) may introduce behavioral changes; review F5 release notes for compatibility notes and deprecated features before upgrading

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
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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