CVE-2025-31644: CVE-2025-31644: When running in Appliance mode, a command injection vulnerability exists in an undisclosed…

What it is

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.

Exploitation evidence

First exploit evidence seen: 2025-05-11 (earliest date across the sources below).

Exploited in the wild

No source on this site lists in-the-wild exploitation yet (CISA KEV, VulnCheck KEV).

Public exploit code

GitHub proof-of-concept repositories

1 public repositories from 1 accounts, first seen 2025-05-11. Most starred: mbadanoiu/CVE-2025-31644 (24 stars), view repository.

Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.

Sources: nomi-sec/PoC-in-GitHub.

How to fix it

Fixed versions

• f5 big-ip access policy manager: upgrade to 15.1.10.7 or later (affected from 15.1.0)
• f5 big-ip advanced firewall manager: upgrade to 15.1.10.7 or later (affected from 15.1.0)
• f5 big-ip advanced web application firewall: upgrade to 15.1.10.7 or later (affected from 15.1.0)
• f5 big-ip analytics: upgrade to 15.1.10.7 or later (affected from 15.1.0)
• f5 big-ip application acceleration manager: upgrade to 15.1.10.7 or later (affected from 15.1.0)
• f5 big-ip application security manager: upgrade to 15.1.10.7 or later (affected from 15.1.0)
• f5 big-ip application visibility and reporting: upgrade to 15.1.10.7 or later (affected from 15.1.0)
• f5 big-ip automation toolchain: upgrade to 15.1.10.7 or later (affected from 15.1.0)
• f5 big-ip carrier-grade nat: upgrade to 15.1.10.7 or later (affected from 15.1.0)
• f5 big-ip container ingress services: upgrade to 15.1.10.7 or later (affected from 15.1.0)
• f5 big-ip ddos hybrid defender: upgrade to 15.1.10.7 or later (affected from 15.1.0)
• f5 big-ip domain name system: upgrade to 15.1.10.7 or later (affected from 15.1.0)
• f5 big-ip edge gateway: upgrade to 15.1.10.7 or later (affected from 15.1.0)
• f5 big-ip fraud protection service: upgrade to 15.1.10.7 or later (affected from 15.1.0)
• f5 big-ip global traffic manager: upgrade to 15.1.10.7 or later (affected from 15.1.0)
• f5 big-ip link controller: upgrade to 15.1.10.7 or later (affected from 15.1.0)
• f5 big-ip local traffic manager: upgrade to 15.1.10.7 or later (affected from 15.1.0)
• f5 big-ip policy enforcement manager: upgrade to 15.1.10.7 or later (affected from 15.1.0)
• f5 big-ip ssl orchestrator: upgrade to 15.1.10.7 or later (affected from 15.1.0)
• f5 big-ip webaccelerator: upgrade to 15.1.10.7 or later (affected from 15.1.0)
• f5 big-ip websafe: upgrade to 15.1.10.7 or later (affected from 15.1.0)
• f5 big-ip access policy manager: upgrade to 16.1.6 or later (affected from 16.1.0)
• f5 big-ip advanced firewall manager: upgrade to 16.1.6 or later (affected from 16.1.0)
• f5 big-ip advanced web application firewall: upgrade to 16.1.6 or later (affected from 16.1.0)
• f5 big-ip analytics: upgrade to 16.1.6 or later (affected from 16.1.0)

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

• https://my.f5.com/manage/s/article/K000148591 (Vendor Advisory)

MITRE ATT&CK mitigations for this chain

• M1048 Application Isolation and Sandboxing (for T1190) : Application isolation will limit what other processes and system features the exploited target can access.
• M1037 Filter Network Traffic (for T1190) : Restrict outbound network traffic from public-facing servers to prevent unauthorized connections from initiating communications with attacker-controlled infrastructure. While this may not prevent the initial exploitation, it limits the attacker's ability to verify and control the compromised server post-exploit, reduci
• M1030 Network Segmentation (for T1190) : Segment externally facing servers and services from the rest of the network with a DMZ or on separate hosting infrastructure.
• M1016 Vulnerability Scanning (for T1190) : Regularly scan externally facing systems for vulnerabilities and establish procedures to rapidly patch systems when critical vulnerabilities are discovered through scanning and through public disclosure.
• M1026 Privileged Account Management (for T1190, T1059) : Use least privilege for service accounts will limit what permissions the exploited process gets on the rest of the system.
• M1050 Exploit Protection (for T1190) : Web Application Firewalls may be used to limit exposure of applications to prevent exploit traffic from reaching the application.
• M1035 Limit Access to Resource Over Network (for T1190) : Ensure that all publicly exposed services are actually intended to be so, and restrict access to any that should only be available internally.
• M1051 Update Software (for T1190) : Update software regularly by employing patch management for externally exposed applications.
• M1033 Limit Software Installation (for T1059) : Prevent user installation of unrequired command and scripting interpreters.
• M1045 Code Signing (for T1059) : Where possible, only permit execution of signed scripts.

Detection Generic guidance

• Initial Access: Alert on unusual requests to the affected service (odd paths, oversized payloads, exploit strings) in WAF, reverse-proxy and application logs.
• Execution: Watch for the service process spawning shells or script interpreters (cmd.exe, powershell, sh, bash, python) via EDR process-tree rules.

Response checklist Generic guidance

1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.