Skip to main content
VulnerabilityPublished Updated

CVE-2025-58153: F5 BIG-IP · Improper Locking

Affects F5 BIG-IPSource CVE Database V5

0

Not known to be exploited · CVSS 5.9 Medium.

Data as of 26 Oct 2026, 10:12 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Oct 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.5.0
  • =16.1.0
  • =15.1.0
Fixed in–

AI-suggested

  1. Monitor network traffic closely for unusual patterns that might trigger the HSB lockup, focusing on traffic anomalies or spikes.
  2. Implement network segmentation to isolate BIG-IP devices and limit exposure to potentially malicious traffic sources.
  3. Restrict access to BIG-IP management interfaces and control plane to trusted networks only.
  4. Engage with F5 Networks support to obtain guidance on interim workarounds or configuration adjustments that may reduce risk.
  5. Plan and prioritize patching as soon as official updates or firmware fixes are released by F5.
  6. Conduct regular backups and maintain redundancy in network infrastructure to minimize downtime in case of device lockup.
  7. Employ network-level DoS protection mechanisms to mitigate potential exploitation attempts.
  8. Test updates and patches in controlled environments before deployment to production to ensure stability.
  9. Maintain an incident response plan that includes procedures for handling BIG-IP outages.
  10. Stay informed through F5 security advisories and trusted vulnerability databases for any changes in exploit status or mitigation recommendations.

Description

Under undisclosed traffic conditions along with conditions beyond the attacker's control, hardware systems with a High-Speed Bridge (HSB) may experience a lockup of the HSB.  Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

References

Community reviews

Loading reviews…