Skip to main content
CVE-2025-61990VulnerabilityPublished Updated

CVE-2025-61990: F5 BIG-IP · Double Free

Affects F5 BIG-IPSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 25 Oct 2026, 19:02 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
F5f5/big-ippkg:rpm/f5/big-ipOther threatsAffected
  • =15.1.0
  • =16.1.0
  • =17.1.0
  • =17.5.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

Organizations should prioritize monitoring for vendor updates and apply patches as soon as they become available from F5 Networks. In the absence of patches, network administrators should consider implementing network-level protections such as filtering or rate-limiting traffic patterns that may trigger the vulnerability, although the exact triggering traffic is undisclosed. Deploying intrusion detection/prevention systems (IDS/IPS) with signatures targeting anomalous traffic to BIG-IP devices may help mitigate exploitation attempts. Segmentation of management and data plane networks can reduce exposure. Regularly auditing and updating BIG-IP configurations to minimize attack surface and disabling unused services or blades can also help. Maintaining up-to-date backups and incident response plans for BIG-IP infrastructure will aid in rapid recovery if exploitation occurs. Close collaboration with F5 support and threat intelligence sharing communities is recommended to stay informed about emerging exploits and mitigation strategies.

Description

When using a multi-bladed platform with more than one blade, 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…