# CVE-2026-2507: BIG-IP TMM Vulnerability

> Attackers can cause a denial of service by triggering a null dereference in TMM when AFM or DDoS protection is enabled.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Feb 2026
- **Updated:** 18 Feb 2026
- **Also known as:** GHSA-chpq-fr33-gp2m

## What is CVE-2026-2507?

CVE-2026-2507 is a high-severity vulnerability in F5 BIG-IP, published on 18 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2026-2507?


## How do I fix CVE-2026-2507?

No fix has been published for CVE-2026-2507 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-2507 being exploited?

There is no known exploitation of CVE-2026-2507 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-2507 and fix it if it is affected.

What it is: CVE-2026-2507 is a high-severity vulnerability in F5 BIG-IP, published on 18 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-2507 in the wild and no public exploit code.

Affected product: F5 BIG-IP. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-2507/ (Markdown: https://insights.sbomify.com/CVE-2026-2507/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-2507
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-2507
- OSV: https://osv.dev/vulnerability/CVE-2026-2507

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-2507/
Summaries are generated and may contain mistakes; the official description above is the record.