Skip to main content
VulnerabilityPublished Updated

CVE-2025-59478: F5 BIG-IP · Access of Uninitialized Pointer

Affects F5 BIG-IPSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 30% 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: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
F5f5/big-ippkg:rpm/f5/big-ipOther threatsAffected
  • =17.5.0
  • =17.1.0
  • =15.1.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Monitor F5 Networks' official security advisories and promptly apply patches or updates once they are released for this vulnerability.
  2. Until patches are available, consider disabling or carefully restricting the use of AFM denial-of-service protection profiles on virtual servers, especially in environments exposed to untrusted networks.
  3. Implement network-level access controls to limit exposure of BIG-IP management and virtual server interfaces to trusted sources only.
  4. Use intrusion detection and prevention systems to monitor for anomalous or crafted traffic patterns that could trigger the vulnerability.
  5. Employ redundancy and failover mechanisms to minimize service disruption if the TMM process crashes.
  6. Conduct regular configuration reviews and security audits of BIG-IP deployments to ensure minimal attack surface.
  7. Engage with F5 support for guidance on temporary workarounds or mitigations specific to your deployment.
  8. Maintain comprehensive logging and monitoring to detect and respond quickly to any exploitation attempts.

Description

When a BIG-IP AFM denial-of-service (DoS) protection profile is configured on a virtual server, undisclosed requests can cause the Traffic Management Microkernel (TMM) process to terminate.  Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

References

Community reviews

Loading reviews…