dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2025-31644

HIGH · 8.7 CVSS v3.1 Published 2025-05-07
Fix available
A fix is available. Upgrade to 15.1.10.7 / 16.1.6 or later.
See remediation →
93/100
Remediation priority · Urgent
Remotely reachable 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 running in Appliance mode, a command injection vulnerability exists in an undisclosed iControl REST and BIG-IP TMOS Shell (tmsh) command which may allow an authenticated attacker with administrator role privileges to execute arbitrary system commands. A successful exploit can allow the attacker to cross a security boundary.  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

F5 BIG-IP systems running in Appliance mode contain a command injection vulnerability in an undisclosed iControl REST and tmsh command. An authenticated attacker with administrator role privileges can execute arbitrary system commands by injecting OS commands through this interface.

MitigationApply F5 vendor patches when available. Restrict administrator access and review iControl REST and tmsh command usage in Appliance mode environments. Consider disabling Appliance mode if not required.

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.7>= 16.1.0, < 16.1.6>= 17.1.0, < 17.1.2.2
Big Ip Advanced Firewall ManagerApplication
Affected:>= 15.1.0, < 15.1.10.7>= 16.1.0, < 16.1.6>= 17.1.0, < 17.1.2.2
Big Ip Advanced Web Application FirewallApplication
Affected:>= 15.1.0, < 15.1.10.7>= 16.1.0, < 16.1.6>= 17.1.0, < 17.1.2.2
Big Ip AnalyticsApplication
Affected:>= 15.1.0, < 15.1.10.7>= 16.1.0, < 16.1.6>= 17.1.0, < 17.1.2.2
Big Ip Application Acceleration ManagerApplication
Affected:>= 15.1.0, < 15.1.10.7>= 16.1.0, < 16.1.6>= 17.1.0, < 17.1.2.2
Big Ip Application Security ManagerApplication
Affected:>= 15.1.0, < 15.1.10.7>= 16.1.0, < 16.1.6>= 17.1.0, < 17.1.2.2
Big Ip Application Visibility And ReportingApplication
Affected:>= 15.1.0, < 15.1.10.7>= 16.1.0, < 16.1.6>= 17.1.0, < 17.1.2.2
Big Ip Automation ToolchainApplication
Affected:>= 15.1.0, < 15.1.10.7>= 16.1.0, < 16.1.6>= 17.1.0, < 17.1.2.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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N

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 installed BIG-IP modules
    Run 'tmsh list sys module' or check the BIG-IP web console for installed modules under System > Package Management
    Affected if Any of these modules are present: APM, AFM, AFW, AAM, ASM, AVR, or Automation Toolchain
  2. Check BIG-IP version
    Run 'tmsh show sys version' or view the version in the web console (Main > Overview > Summary)
    Affected if Version falls within 15.1.0 to 15.1.10.6, 16.1.0 to 16.1.5, or 17.1.0 to 17.1.2.1
  3. Verify Appliance mode is enabled
    Run 'tmsh list sys db ui.appliance-mode' or check the system database setting via 'tmsh list sys db all | grep appliance'
    Affected if The ui.appliance-mode db variable is set to true
  4. Confirm administrator account existence
    Run 'tmsh list auth user' to list local users, or check admin role assignments via 'tmsh list auth role all'
    Affected if Any user with administrator or resource administrator role exists

A user is affected if the BIG-IP version is within the affected ranges AND Appliance mode is enabled AND an administrator-level account is present.

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.10.7 / 16.1.6 / 17.1.2.2 or later
Fixed in 15.1.10.716.1.617.1.2.2
Interim mitigation

Apply F5 vendor patches when available. Restrict administrator access and review iControl REST and tmsh command usage in Appliance mode environments. Consider disabling Appliance mode if not required.

Recommended fix High confidence

15.1.10.7 or later for 15.1.x; 16.1.6 or later for 16.1.x; 17.1.2.2 or later for 17.1.x

  1. Identify the current BIG-IP version by running 'tmsh show sys version' or checking the web UI system information page
  2. Determine which version branch (15.1.x, 16.1.x, or 17.1.x) is currently deployed
  3. Download the appropriate hotfix or upgrade to a fixed version from F5 Downloads at https://downloads.f5.com/ or through the F5 customer portal at my.f5.com
  4. Review F5 upgrade documentation and release notes before upgrading: https://support.f5.com/csp/article/K84555000
  5. Plan maintenance window as upgrades may require system downtime
  6. Back up the BIG-IP configuration using 'tmsh save sys config' before proceeding
  7. For high-availability environments, follow F5 HA upgrade procedures to minimize disruption
  8. Perform the upgrade following F5 installation guidelines for your version
Caveat Review F5 release notes for any configuration or behavioral changes between versions; some upgrades may require additional post-upgrade steps

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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-31644 — 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-31644 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