Threat reportVulnerabilityTL-2026-6570
F5 BIG-IP APM / iRules critical stack-based buffer overflow RCE flaws (CVE-2026-121805, CVE-2026-120292, CVE-2026-120285, CVE-2026-116953, CVE-2026-123637) and APM SAML integer underflow (CVE-2026-126822)
On 2026-11-18 F5 published out-of-band engineering hotfixes for five critical (CVSS v3.1 9.8) stack-based buffer overflows in the BIG-IP data plane (TMM), reachable by unauthenticated remote attackers in specific iRule or APM policy configurations. Impact is TMM termination (traffic outage) with possible remote code execution; F5 lists no mitigations, and no exploitation or public PoC had been reported as of 2026-11-20.
Key facts
| Identifiers | TL-2026-6570, CVE-2026-121805, CVE-2026-120292, CVE-2026-120285, CVE-2026-116953, CVE-2026-123637, CVE-2026-126822, CVE-2026-94127 |
|---|---|
| Severity | CRITICAL |
| CVSS | 9.8 |
| First disclosed | |
| Exploitation status | Linked CVE exploited in the wild; Listed in CISA KEV: CVE-2026-94127 (added ) |
| EPSS | CVE-2026-94127: 1.3% (71.1th percentile); CVE-2026-121805: 0.7% (54.6th percentile); CVE-2026-120292: 0.7% (54.6th percentile) |
| Affected products | F5 BIG-IP (all modules; APM for CVE-2026-123637 and CVE-2026-126822; PEM for CVE-2026-121805); F5 BIG-IP Next for Kubernetes / BIG-IP Next CNF |
| Weaknesses (CWE) | CWE-121 |
| MITRE ATT&CK techniques | T1059 Command and Scripting Interpreter, T1190 Exploit Public-Facing Application, T1499 Endpoint Denial of Service, T1499.004 Application or System Exploitation, T1588.006 Vulnerabilities, T1595.002 Vulnerability Scanning |
| Motivation | UNKNOWN |
| Target sectors | cross-sector |
| Target regions | Global |
| Detection rules | 9 (1 shown free) |
| Sources | 15 cited sources |
Detection coverage
As of 2026-11-21, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-6570 across Splunk SPL, Microsoft KQL and Sigma, covering 14 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.
Free detection: F5 BIG-IP Shell or Download Tool Spawned by tmm Process — Post-Exploitation
Detects a shell, interpreter or download utility executed as a child of the tmm process on a BIG-IP. TMM does not normally spawn interactive shells; the vulnerable TMM overflows (CVE-2026-121805 family) may allow arbitrary code execution, and a post-exploitation shell from tmm would indicate successful RCE.
- Languages: Splunk SPL, Microsoft KQL, Sigma
- ATT&CK: T1059.004, T1059
- Data sources: linux:audit, auditd, sysmon_for_linux
- Severity: critical
- Confidence: high
Splunk SPL
index=linux sourcetype="linux:audit" type=SYSCALL syscall=59 success=yes earliest=-24h
(exe="/bin/bash" OR exe="/bin/sh" OR exe="/usr/bin/curl" OR exe="/usr/bin/wget" OR exe="/usr/bin/python*" OR exe="/usr/bin/perl" OR exe="/usr/bin/nc" OR exe="/usr/bin/ncat" OR exe="/usr/bin/socat")
[ search index=linux sourcetype="linux:audit" type=SYSCALL comm="tmm" earliest=-24h | dedup host pid | rename pid AS ppid | fields host ppid ]
| stats count as exec_count values(exe) as child_exe values(comm) as child_comm values(auid) as auid min(_time) as first_seen by host ppid
| eval first_seen=strftime(first_seen,"%Y-%m-%d %H:%M:%S")
| table host ppid child_exe child_comm auid exec_count first_seenMicrosoft KQL
DeviceProcessEvents
| where Timestamp > ago(24h)
| where InitiatingProcessFileName =~ "tmm" or InitiatingProcessParentFileName =~ "tmm"
| where FileName in~ ("bash", "sh", "dash", "curl", "wget", "python", "python3", "perl", "nc", "ncat", "socat", "busybox")
| project Timestamp, DeviceName, AccountName, FileName, ProcessCommandLine, InitiatingProcessFileName, InitiatingProcessCommandLine, InitiatingProcessParentFileNameSigma
title: F5 BIG-IP Shell Spawned by TMM Process
id: a17e3c58-9d40-4b2f-8c61-4f0b7a2d9e04
status: experimental
description: Detects a shell or interpreter spawned with tmm as the parent on a BIG-IP, indicating possible code execution through the critical TMM stack-based buffer overflows.
references:
- https://my.f5.com/manage/s/article/K000164058
- https://thehackernews.com/2026/11/f5-warns-6-critical-big-ip-flaws-can.html
author: Threadlinqs Team
date: 2026/11/20
tags:
- attack.execution
- attack.t1059.004
- attack.t1059
- cve.2026.121805
- cve.2026.120292
- cve.2026.120285
- cve.2026.116953
- cve.2026.123637
- cve.2026.126822
logsource:
category: process_creation
product: linux
detection:
selection:
ParentImage|endswith: '/tmm'
Image|endswith:
- '/bash'
- '/sh'
- '/dash'
- '/python'
- '/python3'
- '/perl'
condition: selection
falsepositives:
- F5 support or iHealth diagnostic scripts launched by TMM helper tooling
- Administrators running commands from sessions mislabelled as tmm children
level: critical
Known false positives:
- F5 support diagnostic tooling that legitimately forks shells
- Custom iRule-driven automation using exec helpers on older configurations
Tuning notes: Requires auditd execve rules on BIG-IP (or Defender for Endpoint / Sysmon for Linux). Exclude known F5 maintenance scripts by full command line. Any hit on a host also showing SPL-001 TMM crash events should be treated as a likely compromise and the device isolated.
- F5 BIG-IP APM/SAML Endpoint Probing Burst (CVE-2026-126822 / CVE-2026-123637) — Exploitation · unlock with TL Creds
- F5 BIG-IP Interpreter or Network Tool Child of tmm — Post-Exploitation · unlock with TL Creds
- F5 BIG-IP Device Public Egress by Non-Standard Process — C2 / Lateral Movement · unlock with TL Creds
- F5 BIG-IP iRule TCL Errors Referencing Vulnerable Commands (PEM::subscriber, MR::message route, PSC::ip_address, GENERICMESSAGE::route) — Exploitation · unlock with TL Creds
- F5 BIG-IP Download Tool Staging Files in Temp Paths From Appliance Services — Post-Exploitation · unlock with TL Creds
- F5 BIG-IP Netcat/Socat Reverse Shell or Raw TCP Channel — C2 · unlock with TL Creds
- F5 BIG-IP TMM Crash/Restart Indicating Buffer Overflow Exploitation (CVE-2026-121805 family) — Exploitation · unlock with TL Creds
- F5 BIG-IP Periodic Outbound Beaconing to External Hosts — C2 · unlock with TL Creds
Indicators of compromise
As of 2026-11-21, Threadlinqs Intelligence tracks 14 indicators of compromise for TL-2026-6570.
Technical analysis
F5 disclosed 22 advisories on 2026-11-18 (10 for NGINX). Six BIG-IP issues sit in the Traffic Management Microkernel (TMM), the data plane; F5 and secondary sources state there is no control-plane exposure. Five are critical stack-based buffer overflows (CWE-121) rated CVSS v3.1 9.8 and CVSS v4.0 9.3: an unauthenticated remote attacker can terminate TMM, interrupting traffic until it restarts, and may be able to execute arbitrary code on systems with vulnerable configurations. A sixth, CVE-2026-126822, is a high-severity (CVSS 7.5) integer underflow/wraparound in the BIG-IP APM SAML Service Provider function that allows unauthenticated DoS and may allow RCE.
Exploitation is configuration dependent. CVE-2026-121805 requires an iRule that processes client traffic using PEM::subscriber on a virtual server (BIG-IP PEM, BIG-IP Next for Kubernetes, BIG-IP Next CNF). CVE-2026-120292 requires an HTTP profile plus an iRule using MR::message route (all BIG-IP modules, BIG-IP Next for Kubernetes). CVE-2026-120285 requires an HTTP profile plus an iRule using PSC::ip_address (all BIG-IP modules, Next for Kubernetes, Next CNF). CVE-2026-116953 requires a client-traffic iRule using GENERICMESSAGE::route (all BIG-IP modules, Next for Kubernetes). CVE-2026-123637 affects BIG-IP APM only and requires a per-request policy containing both the Client Information agent and the Endpoint Security agents; APM provisioning alone or either agent alone does not meet the condition. CVE-2026-126822 requires an access profile configured as a SAML Service Provider.
Remediation: F5 states there are no mitigations for the five critical flaws; fixes are engineering hotfixes (F5 K000164239 / K000164058; hotfix policy K4918), which do not receive the QA of scheduled releases, and systems already on a custom EHF need a new one from F5 support. Reported BIG-IP fixed builds: 21.1.0 -> BIGIP-21.1.0.4.0.19.3-ENG; 17.5.0 -> BIGIP-17.5.1.11.0.61.12-ENG or BIGIP-17.5.1.10.0.80.35-ENG; 17.1.0 -> BIGIP-17.1.3.7.0.21.4-ENG or BIGIP-17.1.3.6.0.14.20-ENG; Next for Kubernetes -> BNK-2.4.2-EHF1, BNK-2.3.4-EHF1, BNK-2.2.5-EHF1; Next CNF -> CNF-2.4.2-EHF1, CNF-2.3.4-EHF1, CNF-2.2.5-EHF1 (Censys instead lists the BNK builds for CNF; verify with F5). For CVE-2026-126822, THN and BastionZero report a pre-patch reduction: remove the SAML Auth agent if SAML SP is not needed and restrict the virtual server to trusted client networks. Only versions still in F5 technical support were evaluated.
Context: no exploitation was reported at disclosure and Censys found no public PoC. Four of the six were reported to F5 by watchTowr's Sina Kheirkhah (not mapped to specific CVEs); F5 found the other two. Shadowserver (per BleepingComputer, 2026-11-20) tracks 177,000+ exposed BIG-IP instances and 14,600+ IPs with BIG-IP APM fingerprints (honeypot/patched share unknown). Separately, CVE-2026-94127 (APM OAuth Authorization Server heap overflow, F5 K000162605) was exploited as a zero-day RCE and added to CISA KEV on 2026-09-22; it is a distinct flaw, with F5 describing indicators of multiple OAuth authentication failures plus suspicious commands followed by a TMM SIGABRT. CISA has flagged seven F5 flaws as exploited since November 2021, four used by ransomware gangs. The sources contain no network IOCs, so no BeaconBeagle C2 correlation was possible; IOC rows are configuration triggers, process, and fixed-build indicators for exposure assessment. Source disagreements: the CNF fix names above, and the module label on the Next rows of CVE-2026-121805 (PEM vs DNS per Brandefense).
MITRE ATT&CK techniques by tactic:
Execution
T1059 Command and Scripting Interpreter
Initial Access
T1190 Exploit Public-Facing Application
Impact
T1499 Endpoint Denial of Service; T1499.004 Application or System Exploitation
Resource Development
Reconnaissance
Remediation
Patches
- BIGIP-21.1.0.4.0.19.3-ENG
- BIGIP-17.5.1.11.0.61.12-ENG or BIGIP-17.5.1.10.0.80.35-ENG
- BIGIP-17.1.3.7.0.21.4-ENG or BIGIP-17.1.3.6.0.14.20-ENG
- BNK-2.4.2-EHF1 / BNK-2.3.4-EHF1 / BNK-2.2.5-EHF1
- CNF-2.4.2-EHF1 / CNF-2.3.4-EHF1 / CNF-2.2.5-EHF1
Immediate actions
- Install the F5 engineering hotfixes for affected BIG-IP / BIG-IP Next builds (see F5 K000164239 and K000164058); F5 states there are no mitigations for the five critical CVEs
- Inventory virtual servers for iRules using PEM::subscriber, MR::message route, PSC::ip_address or GENERICMESSAGE::route, and APM per-request policies combining Client Information and Endpoint Security agents
- Hosts already running a custom EHF must request a new hotfix from F5 support
Workarounds
- CVE-2026-126822 only: remove the SAML Auth agent if SAML SP is not required and limit virtual server access to trusted client networks
- No vendor workaround for CVE-2026-121805, CVE-2026-120292, CVE-2026-120285, CVE-2026-116953, CVE-2026-123637
Longer-term hardening
- Restrict exposure of APM and data-plane virtual servers to required client networks
- Alert on unexpected TMM restarts/cores and traffic interruptions on BIG-IP
- Review hotfix risk (EHFs skip full QA) and plan upgrade to the next scheduled release containing the fixes
Affected and fixed versions
- F5 — BIG-IP (all modules; APM for CVE-2026-123637 and CVE-2026-126822; PEM for CVE-2026-121805)
Vulnerable versions: 21.1.0 up to fixed build; 17.5.0 up to fixed build; 17.1.0 up to fixed build
Fixed in: BIGIP-21.1.0.4.0.19.3-ENG; 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 - F5 — BIG-IP Next for Kubernetes / BIG-IP Next CNF
Vulnerable versions: 2.4.0-2.4.2; 2.3.0-2.3.4; 2.2.0-2.2.5
Fixed in: BNK-2.4.2-EHF1; BNK-2.3.4-EHF1; BNK-2.2.5-EHF1; CNF-2.4.2-EHF1; CNF-2.3.4-EHF1; CNF-2.2.5-EHF1
Timeline
Last updated · revalidated 1× · latest source
- Start of the period in which, per BleepingComputer, CISA has flagged seven F5 flaws as exploited (four used by ransomware gangs); F5 edge products are a recurring target (date is the 'since November 2021' bound).
- F5 publishes K000162605 for CVE-2026-94127 (APM OAuth Authorization Server RCE), confirmed exploited; CISA adds it to KEV the same day. Separate flaw from this batch.
- F5 reserves CVE-2026-123637 as CNA (APM per-request policy stack-based buffer overflow).
- CISA KEV (2026.11.18, checked by Rescana) does not list CVE-2026-123637; CISA Vulnrichment rates exploitation 'none', automatable 'yes', technical impact 'total'.
- Censys publishes an advisory noting no exploitation reported and no public PoC found as of disclosure.
- F5 releases out-of-band engineering hotfixes (BIGIP-*-ENG, BNK/CNF-*-EHF1); no mitigations offered for the critical CVEs. BIG-IP Next CNF added to affected records.
- F5 publishes 22 advisories (10 NGINX), including five critical BIG-IP stack-based buffer overflows (CVSS v3.1 9.8) and the APM SAML integer underflow CVE-2026-126822 (CVSS 7.5).
- CVE-2026-123637 record updated; F5 revises five of the six overflow advisories (CNF listing), with no change indicated for K000163937.
- BastionZero publishes analysis of the six flaws, noting watchTowr's Sina Kheirkhah reported four of them.
- BleepingComputer reports the emergency patches; Shadowserver tracks 177,000+ exposed BIG-IP instances and 14,600+ IPs with BIG-IP APM fingerprints; no exploitation flagged by F5.
- SecurityOnline (data checked 2026-11-21) still lists no confirmed exploitation for CVE-2026-123637, with 30-day EPSS 0.77%; GBHackers covers the flaw.
Update history
- 2026-11-21 — Critical F5 BIG-IP APM Stack Buffer Overflow (CVE-2026-123637) Enables Unauthenticated TMM Crash and Potential RCE: What changed No severity, exploitability or status change: still CRITICAL / THEORETICAL, with no exploitation, public PoC or KEV listing as of 2026-11-21. The update adds detail only.
Sources cited
- F5 K000163946 (CVE-2026-121805, BIG-IP iRule PEM::subscriber) my.f5.com · Vendor report · 2026-11-18
- F5 K000163940 (CVE-2026-120292) my.f5.com · Vendor report · 2026-11-18
- F5 K000163939 (CVE-2026-120285) my.f5.com · Vendor report · 2026-11-18
- F5 K000163941 (CVE-2026-116953) my.f5.com · Vendor report · 2026-11-18
- F5 K000163937 (CVE-2026-123637, APM) my.f5.com · Vendor report · 2026-11-18
- F5 K000163942 (CVE-2026-126822, APM SAML) my.f5.com · Vendor report · 2026-11-18
- F5 hotfix information K000164239 my.f5.com · Vendor report · 2026-11-18
- F5 security notification K000164058 my.f5.com · Vendor report · 2026-11-18
- Censys advisory: F5 BIG-IP iRule and APM TMM Remote Code Execution censys.com · Research · 2026-11-18
- F5 K000162605 (CVE-2026-94127, APM OAuth) my.f5.com · Vendor report · 2026-09-22
- Brandefense: F5 BIG-IP iRule Vulnerabilities Compared brandefense.io · Blog · 2026-11-18
- BastionZero: F5 BIG-IP Critical Flaws Crash TMM, May Allow RCE bastionzero.com · Blog · 2026-11-19
- BleepingComputer: F5 releases emergency patches for critical BIG-IP RCE flaws BleepingComputer · News · 2026-11-20
- The Hacker News: F5 Warns 6 Critical BIG-IP Flaws Can Crash Traffic in Specific Setups, May Allow RCE The Hacker News · News · 2026-11-18
- BleepingComputer: F5 warns of BIG-IP APM RCE zero-day exploited in attacks (CVE-2026-94127) BleepingComputer · News · 2026-09-23
Previous and next in vulnerability
Drafted by the Threadlinqs research pipeline from 15 sources; published ; last updated .