Skip to main content
VulnerabilityPublished Updated

CVE-2025-20029: F5 BIG-IP · OS Command Injection

Affects F5 BIG-IPSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
7.1% chance of exploitation in 30 days – higher than 94% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Feb 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
F5 BIG-IPAffected
  • =17.1.0
  • =16.1.0
  • =15.1.0
Fixed in–

AI-suggested

  1. Apply official patches from F5 as soon as they become available for the affected BIG-IP versions.
  2. Restrict access to the iControl REST API and TMOS Shell interfaces to trusted administrators only, using network segmentation, VPNs, or firewall rules.
  3. Enforce strong authentication mechanisms and monitor authentication logs for suspicious activity.
  4. Implement strict input validation and command filtering where possible in custom integrations interacting with BIG-IP management interfaces.
  5. Regularly audit and review BIG-IP configurations and access controls to minimize the attack surface.
  6. Employ intrusion detection and prevention systems to detect anomalous command execution attempts.
  7. Maintain up-to-date backups and incident response plans to enable rapid recovery in case of compromise.
  8. Consider deploying compensating controls such as multi-factor authentication and just-in-time access to reduce risk exposure.

Description

Command injection vulnerability exists in iControl REST and BIG-IP TMOS Shell (tmsh) save command, which may allow an authenticated attacker to execute arbitrary system commands. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

References

Community reviews

Loading reviews…