CVE-2026-2507: F5 BIG-IP · NULL Pointer Dereference
Affects F5 BIG-IPSource CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 11:42 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 25% 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 18 Feb 2026
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 |
|---|---|---|
| F5BIG-IP | Affected
| Fixed in– |
AI-suggested
- Immediate monitoring of network traffic for unusual patterns that could trigger the vulnerability is critical.
- Implement network segmentation and access controls to limit exposure of BIG-IP management and data interfaces to untrusted networks.
- Employ rate limiting and anomaly detection to reduce the likelihood of triggering the NULL pointer dereference.
- Maintain up-to-date backups and incident response plans to quickly recover from service disruptions.
- Engage with F5 Networks for early access to patches or workarounds as they become available.
- Consider deploying redundant BIG-IP devices or failover configurations to maintain availability during an attack.
- Regularly audit and review BIG-IP configurations to ensure minimal attack surface and adherence to security best practices.
- Coordinate with upstream ISPs and security vendors to detect and mitigate potential attack traffic before it reaches critical infrastructure.
Description
When BIG-IP AFM or BIG-IP DDoS is provisioned, undisclosed traffic can cause TMM to terminate. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.