# CVE-2026-123637: BIG-IP APM Vulnerability

> Unauthenticated remote attackers can crash TMM on BIG-IP APM with certain per-request policies, causing DoS and possibly RCE.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/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
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 18 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-q3pc-8x94-2vq5

## What is CVE-2026-123637?

CVE-2026-123637 is a critical memory corruption vulnerability in F5 BIG-IP, published on 18 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

When BIG-IP APM is provisioned and a per-request policy that includes the Client Information agent and Endpoint Security agents is applied to a virtual server, undisclosed requests can cause the Traffic Management Microkernel (TMM) to terminate and may lead to remote code execution (RCE).

Impact:

Traffic is disrupted while the TMM process restarts. This vulnerability allows a remote, unauthenticated attacker to cause a denial-of-service (DoS) on the BIG-IP system and may allow the attacker to perform RCE. There is no control plane exposure; this is a data plane issue only.

Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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

Only installations with a non-default setting turned on are exposed.


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

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

## Is CVE-2026-123637 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-123637 is a critical memory corruption vulnerability in F5 BIG-IP, published on 18 Nov 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-123637 in the wild and no public exploit code.
Exposure: Only installations with a non-default setting turned on are exposed.

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-123637/ (Markdown: https://insights.sbomify.com/CVE-2026-123637/index.md)
```

## Sources

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

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