CVE-2025-54858: F5 BIG-IP · Uncontrolled Recursion
Affects F5 BIG-IPSource CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation 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 BIG-IP | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-54858, organizations should first verify if their BIG-IP deployments use Advanced WAF or ASM modules with JSON content profiles containing malformed JSON schemas. Immediate steps include reviewing and correcting JSON schema configurations to ensure they are well-formed and validated before applying security policies. Administrators should avoid deploying policies with unverified or complex JSON schemas that could trigger recursion. Applying vendor patches or updates as soon as they become available is critical, even though no patches are currently listed, monitoring F5 advisories for updates is necessary. As a temporary workaround, disabling or removing JSON content profiles from security policies can reduce exposure. Network-level protections such as rate limiting and anomaly detection can help identify and block malformed requests targeting this vulnerability. Regularly auditing BIG-IP configurations and employing automated schema validation tools can prevent recurrence. Additionally, implementing redundancy and failover mechanisms for BIG-IP devices can minimize service disruption if the bd process terminates unexpectedly. Finally, maintaining up-to-date backups and incident response plans will aid in rapid recovery if exploitation occurs.
Description
When a BIG-IP Advanced WAF or BIG-IP ASM Security Policy is configured with a JSON content profile that has a malformed JSON schema, and the security policy is applied to a virtual server, undisclosed requests can cause the bd process to terminate. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.