CVE-2026-22548: F5 BIG-IP · Race Condition
Affects F5 BIG-IPSource CVE Database V5
Not known to be exploited · CVSS 5.9 Medium : upgrade to 17.1.3 when convenient.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 17.1.3
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 4 Feb 2026
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 2026-10-25.
What to do
Upgrade F5 BIG-IP to 17.1.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| F5BIG-IP | Affected
| Fixed in
|
AI-suggested
1. Monitor bd process stability closely on all BIG-IP devices running version 17.1.0 with Advanced WAF or ASM policies configured, using system logs and health checks to detect unexpected terminations. 2. Limit exposure of vulnerable virtual servers by restricting access through network segmentation, firewall rules, or IP whitelisting to reduce attack surface. 3. Implement redundancy and failover mechanisms for BIG-IP devices to maintain availability if the bd process crashes. 4. Engage with F5 support and subscribe to security advisories to receive updates and patches promptly once available. 5. Conduct controlled testing in staging environments to understand triggering conditions and develop incident response playbooks. 6. Review and harden security policies to minimize complex or unnecessary configurations that might increase race condition risk. 7. Consider upgrading to supported versions beyond 17.1.0 if patches are unavailable or if EoTS versions are in use. 8. Employ network-level anomaly detection to identify unusual request patterns that could trigger the vulnerability. These steps go beyond generic advice by focusing on process monitoring, access control, and operational resilience tailored to the specific vulnerability characteristics.
Description
When a BIG-IP Advanced WAF or ASM security policy is configured on a virtual server, undisclosed requests along with conditions beyond the attacker's control can cause the bd process to terminate. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.