Introduction
An unauthenticated attacker who can send traffic to a particular kind of BIG-IP virtual server can crash the Traffic Management Microkernel (TMM), interrupting every flow the device handles until TMM restarts. F5 says the same bug may lead to remote code execution. TMM is the data plane process that sits in front of production applications. CVE-2026-120285 matters most to teams that use the PSC::ip_address iRules command on virtual servers with an HTTP profile.
F5 rates the issue Critical: 9.8 under CVSS v3.1 and 9.3 under CVSS v4.0. The fix shipped on November 18, 2026 as part of an out-of-band Security Notification (K000164058) covering several critical BIG-IP iRule and APM flaws, and it is available only as engineering hotfixes. Sina Kheirkhah (SinSinology) of watchTowr reported the issue.
Technical Information
Root cause
F5 classifies the flaw in TMM as CWE-121 (Stack-based Buffer Overflow). The vulnerable component is the PSC::ip_address iRules command. When an iRule using this command is attached to a virtual server that also has an HTTP profile, undisclosed requests can overflow a stack buffer while TMM processes that command, and TMM terminates.
BIG-IP is closed source, and F5 has not published a diff, the size or location of the affected buffer, or the request contents that trigger it. F5 tracks the bug as ID 2719389 for BIG-IP and ID 2719581 for CNF and BIG-IP Next for Kubernetes. Any more specific description of the code path would be speculation, so we stop here.
Preconditions
All three of the following must be true for the bug to be reachable:
- The device runs a vulnerable build (see Affected Systems and Versions).
- A virtual server has an HTTP profile attached.
- The same virtual server has an iRule containing
PSC::ip_address.
The CVSS v3.1 scoring reflects network attack vector, low attack complexity, no privileges required, and no user interaction. F5 states this is a data plane issue only, with no control plane exposure, so management interfaces are not the attack surface.
Attack flow
Based on the advisory, exploitation looks like this:
- The attacker identifies a reachable virtual server that has an HTTP profile and an iRule invoking
PSC::ip_address. - Without authentication, the attacker sends the undisclosed request pattern to that virtual server.
- TMM processes the request through the iRule, and its handling of
PSC::ip_addressoverflows a stack buffer. - TMM terminates and restarts. Traffic through the device is disrupted during the restart, producing a denial of service. Repeating the request can repeat the outage.
- F5 states the flaw may also lead to remote code execution. The published material does not establish under which conditions RCE is achievable.
What is not public
F5 has not disclosed request contents, an exploit procedure, or RCE conditions, and we found no verified proof of concept in the sources we reviewed.
Patch Information
F5 lists the mitigation as "None". An attacker-reachable stack overflow cannot be safely blocked by configuration on a live system, so the engineering hotfixes (EHFs) are the only vendor fix. All builds come from advisory K000163939.
BIG-IP (all modules) 21.x
- Vulnerable: 21.1.0
- Fixed:
BIGIP-21.1.0.4.0.19.3-ENG
BIG-IP (all modules) 17.x
- Vulnerable: 17.5.0 through 17.5.1, and 17.1.0 through 17.1.3
- Fixed:
BIGIP-17.5.1.11.0.61.12-ENG,BIGIP-17.5.1.10.0.80.35-ENG,BIGIP-17.1.3.7.0.21.4-ENG,BIGIP-17.1.3.6.0.14.20-ENG
BIG-IP CNF 2.x
- Vulnerable: 2.4.0 through 2.4.2, 2.3.0 through 2.3.4, and 2.2.0 through 2.2.5
- Fixed:
CNF-2.4.2-EHF1,CNF-2.3.4-EHF1,CNF-2.2.5-EHF1
BIG-IP Next for Kubernetes 2.x
- Vulnerable: 2.4.0 through 2.4.2, 2.3.0 through 2.3.4, and 2.2.0 through 2.2.5
- Fixed:
BNK-2.4.2-EHF1,BNK-2.3.4-EHF1,BNK-2.2.5-EHF1
A note on CNF: the patch information we reviewed lists CNF as vulnerable with the EHF builds above, while one summary of the advisory product table we reviewed marked BIG-IP CNF as not vulnerable. CNF operators should confirm their status directly in K000163939.
Choosing the right 17.x or 21.x build
Each 17.x branch has two fixed builds because F5 rebuilt the fix on top of existing hotfix lines. Per companion article K000164239:
BIGIP-17.1.3.7.0.21.4-ENG: systems on the 17.1.3.7 base release or any earlier base release.BIGIP-17.1.3.6.0.14.20-ENG: only systems already runningBIGIP-17.1.3.6.0.9.20-ENG.BIGIP-17.5.1.11.0.61.12-ENG: systems on the 17.5.1.11 base release or any earlier base release.BIGIP-17.5.1.10.0.80.35-ENG: only systems already runningBIGIP-17.5.1.10.0.7.35-ENGorBIG-IP-17.5.1.10.0.37.35-ENG.BIGIP-21.1.0.4.0.19.3-ENG: systems on the 21.1.0.4 base release or any earlier base release.- Custom EHF builds: contact F5 Support for a new engineering hotfix, since a custom build will not line up with any published one.
This lets sites already on an EHF keep earlier fixes instead of falling back to a base release.
Caveats
- EHFs are not scheduled releases. F5 notes they "do not undergo the extensive QA assessment of scheduled software releases" and offers them without warranty. Test in staging before production.
- The builds are on MyF5 Downloads, not a public mirror, so you need a MyF5 account to get them.
- The fix carries forward. Under F5's versioning policy, once a fix lands in a branch it is included in all later minor, maintenance and point releases of that branch. When a scheduled release containing bug 2719389 or 2719581 ships, you can move from the EHF to it and stay protected.
To check coverage, compare your running version with the "Versions known to be vulnerable" column. If "Fixes introduced in" lists an earlier build in your branch, F5 says your version should already have the fix.
F5 lists BIG-IQ, F5 Insight, F5OS (including the A and C variants), NGINX, F5 Distributed Cloud and AI Gateway as not vulnerable.
Detection Methods
No public exploit signatures exist yet. As of November 18, 2026, CVETodo's coverage check listed no Sigma, Suricata, YARA or Nuclei rules, and none of the reviewed sources gave CVE-specific IoCs or log patterns. For now, detection comes down to finding exposed systems and watching for the crash this bug causes.
1. Configuration-aware exposure assessment
A version scanner alone will over-report. To assess real exposure:
- Enumerate every iRule that uses
PSC::ip_address. - Identify which virtual servers have one of those iRules together with an HTTP profile.
- Cross-reference against the vulnerable version ranges.
A vulnerable build without that combination is not reachable through this bug. A vulnerable build with that combination on an internet-facing virtual server should be your top priority. Since there is no control plane exposure, map traffic-facing virtual servers rather than management interfaces.
2. F5 iHealth with a QKView
The advisory states iHealth can diagnose this vulnerability on BIG-IP systems. Per K27404821:
- Generate a QKView diagnostic archive on the device and upload it to ihealth.f5.com.
- Open the QKView and go to Diagnostics. iHealth compares logs, command output and configuration with F5's vulnerability database.
- For a single object, open Config Explorer, then LTM, choose the object type (virtual servers or iRules), select the object, and open its Diagnostics tab.
Matches link back to K000163939. F5 says generating and reviewing the QKView has no impact on the system. iHealth identifies vulnerable or exposed systems. It does not determine whether a device has already been exploited.
3. Runtime symptom: unexpected TMM restarts
The only documented observable effect is TMM terminating and traffic being disrupted during the restart. Given the CWE-121 classification, failed or crude exploitation attempts are likely to surface as TMM crashes. Watch for:
- unplanned TMM terminations or restarts, and drops in data plane availability, on systems that meet the preconditions
- crash events coinciding with HTTP traffic to virtual servers running a
PSC::ip_addressiRule
Treat repeated restarts as possible exploitation attempts, not routine instability.
Because F5 says the flaw "may lead to remote code execution", a clean crash history does not rule out a quieter, successful attack. For devices exposed before patching, treat iHealth results and crash monitoring as triage signals, not proof that nothing happened.
Affected Systems and Versions
Vulnerable versions per F5:
- BIG-IP (all modules) 21.x: 21.1.0
- BIG-IP (all modules) 17.x: 17.5.0 through 17.5.1, and 17.1.0 through 17.1.3
- BIG-IP Next for Kubernetes 2.x: 2.4.0 through 2.4.2, 2.3.0 through 2.3.4, and 2.2.0 through 2.2.5
- BIG-IP CNF 2.x: 2.4.0 through 2.4.2, 2.3.0 through 2.3.4, and 2.2.0 through 2.2.5 per the patch information reviewed (verify against K000163939, as noted above)
Vulnerable configuration: a virtual server with an HTTP profile and an iRule containing the PSC::ip_address command.
F5 did not evaluate software versions that have reached End of Technical Support (EoTS).
Vendor Security History
This CVE was published alongside several other critical BIG-IP iRule and APM flaws in Security Notification K000164058. The Hacker News reported six critical BIG-IP flaws that can crash traffic in specific setups and may allow RCE, without any statement that they had been exploited.
Separately, F5 previously disclosed (K000154696) that a nation-state threat actor had persistent access to certain F5 systems and exfiltrated files from its BIG-IP development and engineering knowledge management environments, including some BIG-IP source code and information about undisclosed vulnerabilities. F5 stated it had no evidence of software supply chain modification, an assessment independently reviewed by NCC Group and IOActive. That disclosure does not link the incident or actor to CVE-2026-120285.
No reviewed source confirms in-the-wild exploitation of CVE-2026-120285, and it was not in the CISA KEV catalog at the time of review. Absence from the catalog is limited evidence, not proof that exploitation has not occurred.
References
- NVD: CVE-2026-120285
- CVE Record: CVE-2026-120285
- F5 Advisory K000163939: BIG-IP iRule vulnerability CVE-2026-120285
- F5 K000164239: Engineering hotfix guidance
- F5 K000164058: Security Notification
- F5 K27404821: iHealth diagnostics
- CVETodo: CVE-2026-120285
- The Hacker News: F5 Warns 6 Critical BIG-IP Flaws Can Crash Traffic in Specific Setups, May Allow RCE
- CISA Known Exploited Vulnerabilities Catalog
- F5 Security Incident K000154696
- F5 BIG-IP product overview
- F5 SEC filing



