CVE
F5 BIG-IP remote code execution in TMM via PEM iRule
- Exploited
- No known exploitation
- Fix
- Fixed in BIG-IP BIGIP-21.1.0.4.0.19.3-ENG, BIGIP-17.5.1.11.0.61.12-ENG, BIGIP-17.1.3.7.0.21.4-ENG · BIG-IP Next for Kubernetes BNK-2.4.2-EHF1, BNK-2.3.4-EHF1, BNK-2.2.5-EHF1 · BIG-IP Next CNF BNK-2.4.2-EHF1, BNK-2.3.4-EHF1, BNK-2.2.5-EHF1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: BIG-IP BIGIP-21.1.0.4.0.19.3-ENG, BIGIP-17.5.1.11.0.61.12-ENG, BIGIP-17.1.3.7.0.21.4-ENG · BIG-IP Next for Kubernetes BNK-2.4.2-EHF1, BNK-2.3.4-EHF1, BNK-2.2.5-EHF1 · BIG-IP Next CNF BNK-2.4.2-EHF1, BNK-2.3.4-EHF1, BNK-2.2.5-EHF1.
Summary
The BIG-IP and BIG-IP Next for Kubernetes products are affected when an iRule that uses the PEM::subscriber command runs on a virtual server. A remote attacker without logging in can send specially crafted traffic that crashes the Traffic Management Microkernel (TMM), disrupting traffic, and may be able to run code on the system.
Original description
Description:
When an iRule that processes client traffic using the PEM::subscriber command is configured on 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 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.
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.8, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 35 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: BIG-IP BIGIP-21.1.0.4.0.19.3-ENG, BIGIP-17.5.1.11.0.61.12-ENG, BIGIP-17.1.3.7.0.21.4-ENG · BIG-IP Next for Kubernetes BNK-2.4.2-EHF1, BNK-2.3.4-EHF1, BNK-2.2.5-EHF1 · BIG-IP Next CNF BNK-2.4.2-EHF1, BNK-2.3.4-EHF1, BNK-2.2.5-EHF1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-121805 (BIG-IP iRule Vulnerability), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-121805 (entry last updated 2026-11-18):
Affected:
- F5 BIG-IP: from 21.1.0, fixed in BIGIP-21.1.0.4.0.19.3-ENG; from 17.5.0, fixed in BIGIP-17.5.1.11.0.61.12-ENG; from 17.1.0, fixed in BIGIP-17.1.3.7.0.21.4-ENG
- F5 BIG-IP Next for Kubernetes: from 2.4.0, fixed in BNK-2.4.2-EHF1; from 2.3.0, fixed in BNK-2.3.4-EHF1; from 2.2.0, fixed in BNK-2.2.5-EHF1
- F5 BIG-IP Next CNF: from 2.4.0, fixed in BNK-2.4.2-EHF1; from 2.3.0, fixed in BNK-2.3.4-EHF1; from 2.2.0, fixed in BNK-2.2.5-EHF1
Fixed versions: BIGIP-21.1.0.4.0.19.3-ENG, BIGIP-17.5.1.11.0.61.12-ENG, BIGIP-17.1.3.7.0.21.4-ENG, BNK-2.4.2-EHF1, BNK-2.3.4-EHF1, BNK-2.2.5-EHF1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-121805 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-121805 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://my.f5.com/manage/s/article/K000163946
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-121805
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-121805"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- cve.now early warning
F5 warns six critical BIG-IP flaws can crash traffic and may allow code execution
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- F5 BIG-IP
From 21.1.0 · fixed in BIGIP-21.1.0.4.0.19.3-ENG; From 17.5.0 · fixed in BIGIP-17.5.1.11.0.61.12-ENG; From 17.1.0 · fixed in BIGIP-17.1.3.7.0.21.4-ENG
- F5 BIG-IP Next for Kubernetes
From 2.4.0 · fixed in BNK-2.4.2-EHF1; From 2.3.0 · fixed in BNK-2.3.4-EHF1; From 2.2.0 · fixed in BNK-2.2.5-EHF1
- F5 BIG-IP Next CNF
From 2.4.0 · fixed in BNK-2.4.2-EHF1; From 2.3.0 · fixed in BNK-2.3.4-EHF1; From 2.2.0 · fixed in BNK-2.2.5-EHF1
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-121805 |
| Record | NVD · CVE-2026-121805 |
| Other links 1 | |
| Patch | my.f5.com · manage/s/article/K000163946 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-121805
Is CVE-2026-121805 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-121805?
BIG-IP: from 21.1.0 before BIGIP-21.1.0.4.0.19.3-ENG; from 17.5.0 before BIGIP-17.5.1.11.0.61.12-ENG; from 17.1.0 before BIGIP-17.1.3.7.0.21.4-ENG. BIG-IP Next for Kubernetes: from 2.4.0 before BNK-2.4.2-EHF1; from 2.3.0 before BNK-2.3.4-EHF1; from 2.2.0 before BNK-2.2.5-EHF1. BIG-IP Next CNF: from 2.4.0 before BNK-2.4.2-EHF1; from 2.3.0 before BNK-2.3.4-EHF1; from 2.2.0 before BNK-2.2.5-EHF1.Source: cve.now feed data
How do I fix CVE-2026-121805?
Upgrade to a fixed version: BIG-IP BIGIP-21.1.0.4.0.19.3-ENG, BIGIP-17.5.1.11.0.61.12-ENG, BIGIP-17.1.3.7.0.21.4-ENG · BIG-IP Next for Kubernetes BNK-2.4.2-EHF1, BNK-2.3.4-EHF1, BNK-2.2.5-EHF1 · BIG-IP Next CNF BNK-2.4.2-EHF1, BNK-2.3.4-EHF1, BNK-2.2.5-EHF1.Source: cve.now feed data