CVE-2025-58096: F5 BIG-IP · Out-of-bounds Write
Affects F5 BIG-IPSource CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 14:05 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
- Review and revert the tm.tcpudptxchecksum database variable to its default setting if it is currently set to 'Software-only', unless this configuration is explicitly required for operational reasons.
- Implement network-level protections such as ingress filtering and firewall rules to restrict access to BIG-IP management and traffic interfaces, limiting exposure to untrusted networks.
- Monitor BIG-IP system logs and TMM process health closely for signs of unexpected terminations or crashes that may indicate exploitation attempts.
- Engage with F5 Networks support and subscribe to their security advisories for updates on patches or official mitigations as they become available.
- Consider deploying redundant BIG-IP devices or failover configurations to minimize service disruption in case of TMM crashes.
- Conduct internal penetration testing or vulnerability assessments to verify the presence of this vulnerability and effectiveness of mitigations.
- Limit exposure of BIG-IP devices to the internet or untrusted networks where possible, using VPNs or secure tunnels for remote access.
- Prepare incident response plans specifically addressing potential denial-of-service scenarios involving BIG-IP devices to ensure rapid recovery.
Description
When the database variable tm.tcpudptxchecksum is configured as non-default value Software-only on a BIG-IP system, undisclosed traffic can cause the Traffic Management Microkernel (TMM) to terminate. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.