Skip to main content
CVE-2025-54479VulnerabilityPublished Updated

CVE-2025-54479: F5 BIG-IP · Out-of-bounds Write

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
  • =17.5.0
  • =17.1.0
  • =16.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. Review and audit BIG-IP virtual server configurations to ensure that classification profiles are not applied without an HTTP or HTTP/2 profile. 2. Temporarily disable or remove classification profiles on virtual servers lacking HTTP/HTTP2 profiles until patches are available. 3. Monitor F5 Networks advisories closely for official patches or hotfixes addressing CVE-2025-54479 and apply them promptly once released. 4. Implement network-level protections such as rate limiting and traffic filtering to reduce exposure to malformed or unexpected requests targeting BIG-IP devices. 5. Employ redundancy and failover mechanisms in BIG-IP deployments to minimize service disruption in case of TMM termination. 6. Conduct regular vulnerability assessments and penetration testing focusing on BIG-IP configurations to detect potential misconfigurations or exploitable conditions. 7. Maintain up-to-date inventory of BIG-IP versions in use and plan for timely upgrades to supported versions with security fixes. 8. Engage with F5 support for guidance on interim mitigations and best practices specific to your deployment environment.

Description

When a classification profile is configured on a virtual server without an HTTP or HTTP/2 profile, undisclosed requests 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…