dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2025-21091

HIGH · 7.5 CVSS v3.1 Published 2025-02-05
Fix available
A fix is available. Upgrade to 16.1.6 / 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 SNMP v1 or v2c are disabled on the BIG-IP, 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

In F5 BIG-IP systems, when SNMP v1 or v2c protocols are disabled, certain undisclosed network requests can trigger excessive memory consumption. This memory exhaustion vulnerability can lead to denial of service conditions, potentially rendering the device unresponsive or causing instability.

MitigationApply the vendor-supplied patch when available. Until then, monitor memory utilization on affected BIG-IP devices and consider network segmentation to limit exposure to unauthenticated requests targeting the SNMP service.

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.6>= 17.1.0, < 17.1.2
Big Ip Advanced Firewall ManagerApplication
Affected:>= 15.1.0, <= 15.1.10>= 16.1.0, < 16.1.6>= 17.1.0, < 17.1.2
Big Ip Advanced Web Application FirewallApplication
Affected:>= 15.1.0, <= 15.1.10>= 16.1.0, < 16.1.6>= 17.1.0, < 17.1.2
Big Ip AnalyticsApplication
Affected:>= 15.1.0, <= 15.1.10>= 16.1.0, < 16.1.6>= 17.1.0, < 17.1.2
Big Ip Application Acceleration ManagerApplication
Affected:>= 15.1.0, <= 15.1.10>= 16.1.0, < 16.1.6>= 17.1.0, < 17.1.2
Big Ip Application Security ManagerApplication
Affected:>= 15.1.0, <= 15.1.10>= 16.1.0, < 16.1.6>= 17.1.0, < 17.1.2
Big Ip Application Visibility And ReportingApplication
Affected:>= 15.1.0, <= 15.1.10>= 16.1.0, < 16.1.6>= 17.1.0, < 17.1.2
Big Ip Automation ToolchainApplication
Affected:>= 15.1.0, <= 15.1.10>= 16.1.0, < 16.1.6>= 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 device and version
    Run command: tmsh show /sys version | grep -i version or check /etc/oracle-release and the BIG-IP version displayed in the admin console
    Affected if The installed version falls within 15.1.0-15.1.10, 16.1.0-16.1.5, or 17.1.0-17.1.1 (note: 16.1.6+ and 17.1.2+ are not affected)
  2. Check if SNMP v1 or v2c is disabled
    Run: tmsh list /sys snmp community or tmsh show /sys snmp for SNMP configuration details. Look for community entries and their version settings.
    Affected if SNMP v1 or v2c communities are explicitly disabled or not configured (the vulnerability triggers when these protocols are disabled)
  3. Verify SNMP service status
    Run: tmsh list /sys snmp or check the BIG-IP GUI under System > SNMP > Configuration
    Affected if SNMP is enabled but v1/v2c access is restricted or removed, creating the condition for the vulnerability to trigger

You are affected if you run a BIG-IP version in the ranges 15.1.0-15.1.10, 16.1.0-16.1.5, or 17.1.0-17.1.1 AND have SNMP v1/v2c disabled while SNMP remains accessible to network requests.

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.6 / 17.1.2 or later
Fixed in 16.1.617.1.2
Interim mitigation

Apply the vendor-supplied patch when available. Until then, monitor memory utilization on affected BIG-IP devices and consider network segmentation to limit exposure to unauthenticated requests targeting the SNMP service.

Recommended fix High confidence

15.1.11 (for 15.1.x); 16.1.6 (for 16.1.x); 17.1.2 (for 17.1.x)

  1. 1. Identify the current BIG-IP version by running `tmsh show sys version` or checking the web UI.
  2. 2. Determine which major version branch you are on (15.1.x, 16.1.x, or 17.1.x).
  3. 3. For 15.1.0-15.1.10: Upgrade to version 15.1.11 or later.
  4. 4. For 16.1.0-16.1.5: Upgrade to version 16.1.6 or later.
  5. 5. For 17.1.0-17.1.1: Upgrade to version 17.1.2 or later.
  6. 6. After upgrade, verify the fix by confirming the new version is running: `tmsh show sys version`.
Caveat Review F5 release notes for any compatibility notes before upgrading; ensure adequate downtime window for upgrade procedure

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 / QA2.0 h
14.0 hours of engineering $2,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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