CVE-2025-60013: F5 F5OS – Appliance · OS Command Injection
Affects F5 F5OS – ApplianceSource CVE Database V5
Not known to be exploited · CVSS 4.6 Medium.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 15 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| F5 F5OS - Appliance | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-60013, organizations should first avoid using passwords containing special shell metacharacters when initializing the rSeries FIPS module on affected F5OS appliances. Administrators should enforce strong password policies that exclude such characters or ensure proper input validation. It is critical to monitor and restrict access to highly privileged accounts to minimize the risk of exploitation. Organizations should apply vendor patches or updates as soon as they become available, even though no patches are currently listed, maintaining close communication with F5 for security advisories. Implementing strict role-based access controls (RBAC) and auditing privileged user activities can help detect and prevent misuse. Network segmentation and limiting local access to management interfaces reduce the likelihood of an attacker gaining the required privileges. Additionally, organizations should regularly review and update their security configurations to ensure compliance with best practices and FIPS requirements. Finally, consider deploying intrusion detection systems (IDS) or endpoint detection and response (EDR) solutions to identify suspicious command execution attempts on these appliances.
Description
When a highly-privileged, authenticated attacker attempts to initialize the rSeries FIPS module using a password with special shell metacharacters, arbitrary system commands may be executed, and the FIPS hardware security module (HSM) may fail to initialize. 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.