CVE-2026-120285 json
BIG-IP iRule Vulnerability
published 10h ago modified 3h ago also EUVD-2026-128954
- cvss
- 9.3
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
Description When an HTTP profile and an iRule containing the PSC::ip_address command are 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 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.
Patch / fix
- F5 BIG-IP BIGIP-17.1.3.6.0.14.20-ENG, BIGIP-17.1.3.7.0.21.4-ENG, BIGIP-17.5.1.10.0.80.35-ENG, BIGIP-17.5.1.11.0.61.12-ENG, BIGIP-21.1.0.4.0.19.3-ENG
- F5 BIG-IP Next for Kubernetes BNK-2.2.5-EHF1, BNK-2.3.4-EHF1, BNK-2.4.2-EHF1
- F5 BIG-IP Next CNF BNK-2.2.5-EHF1, BNK-2.3.4-EHF1, BNK-2.4.2-EHF1
Is CVE-2026-120285 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 9h ago
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 4.0 | 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 |
Affected products
- F5 BIG-IP
- F5 BIG-IP Next for Kubernetes
- F5 BIG-IP Next CNF
Classification
- Weakness
-
- CWE-121 Stack-based Buffer Overflow
References
-
my.f5.com
/manage/s/article/K000163939
vendor-advisory, patch
Sources
- CVE List CVE-2026-120285
- NVD CVE-2026-120285
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.