Skip to main content
VulnerabilityPublished Updated

CVE-2025-61960: F5 BIG-IP · NULL Pointer Dereference

Affects F5 BIG-IPSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 11:42 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 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: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
  • =17.1.0
  • =16.1.0
Fixed in–

AI-suggested

To mitigate CVE-2025-61960, organizations should first review their BIG-IP configurations to identify if per-request policies are enabled on APM portal access virtual servers. If such policies are not essential, consider disabling them temporarily until patches are available. Monitor BIG-IP system logs and TMM process health closely for signs of unexpected termination or crashes. Implement network-level protections such as rate limiting and traffic filtering to reduce exposure to potentially malformed or undisclosed traffic patterns that could trigger the vulnerability. Stay informed by subscribing to F5 security advisories and promptly apply vendor-released patches or updates once they become available. In environments where patching cannot be immediate, consider deploying redundant BIG-IP devices or failover mechanisms to maintain service availability. Additionally, conduct regular backups of BIG-IP configurations and ensure incident response plans include procedures for rapid recovery from TMM process failures. Engage with F5 support for guidance and potential workarounds specific to your deployment.

Description

When a per-request policy is configured on a BIG-IP APM portal access virtual server, 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.

References

Community reviews

Loading reviews…