CVE-2026-126822 in f5 big-ip
Exploitation of this CVE does not show up in logs, so there is no detection rule for it.
What the vulnerability is
Description: When BIG-IP APM is provisioned, an Access Profile is configured as a SAML SP (Service Provider) and is applied to a virtual server, undisclosed requests can cause the Traffic Management Microkernel (TMM) to terminate. 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. 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.
Affected software: f5 big-ip
Scores
- CVSS: 8.7 (high)
- EPSS: 0.48% chance of exploitation in the next 30 days
- CISA KEV: Not listed
- Published: 2026-11-18
What LogPulse has for it
- Detection rule: No
- Agent check (vulnerable version): No
- Mitigation: Yes, see below
How to mitigate it
Install the F5 out-of-band BIG-IP hotfix for the TMM RCE flaws (November 2026)
Patch or upgrade. F5 fixed five critical stack overflows in BIG-IP TMM (APM per-request policies and four iRule commands) and an APM SAML SP crash. Unauthenticated data plane traffic can crash TMM and may lead to code execution; F5 gives no workaround, so the out-of-band hotfix is the fix.
Applies to: F5 BIG-IP (and BIG-IP Next for Kubernetes for the iRule CVEs) on supported branches without the November 2026 out-of-band hotfix, when the listed APM features or iRule commands are configured.
- List every BIG-IP and BIG-IP Next for Kubernetes instance and note its version with 'tmsh show sys version'.
- Check whether a box is exposed: APM provisioned with a per-request policy that uses the Client Information and Endpoint Security agents (CVE-2026-123637), APM SAML SP access profiles (CVE-2026-126822), or iRules on virtual servers that use PEM::subscriber, MR::message route, PSC::ip_address or GENERICMESSAGE::route (search with 'tmsh list ltm rule' and grep for those commands).
- Open F5 K000164239 for the out-of-band hotfix that matches your branch (engineering hotfixes are linked from K000164058) and the per-CVE articles K000163937, K000163946, K000163940, K000163939, K000163941 and K000163942.
- Take a UCS backup, then install the hotfix on the standby unit first, fail over and install it on the other unit.
- Versions at End of Technical Support are not evaluated by F5: upgrade those to a supported branch with the fix.
- Until patched, prioritise boxes whose affected virtual servers face the internet, and watch for unexpected TMM restarts (tmm core files in /var/core, 'TMM restarted' messages in /var/log/ltm).
- After patching, confirm the version with 'tmsh show sys version' and let the vulnerability scan stop reporting the CVEs.
Sources:
- https://my.f5.com/manage/s/article/K000163937
- https://my.f5.com/manage/s/article/K000163946
- https://my.f5.com/manage/s/article/K000163940
- https://my.f5.com/manage/s/article/K000163939
- https://my.f5.com/manage/s/article/K000163941
- https://my.f5.com/manage/s/article/K000163942
- https://www.bleepingcomputer.com/news/security/f5-releases-emergency-patches-for-critical-big-ip-rce-flaws/
In the news
1 publication wrote about this CVE in the last 14 days, most recently on 2026-11-20.
- F5 releases emergency patches for critical BIG-IP RCE flaws (BleepingComputer, 2026-11-20)
Source data: NIST NVD, CISA KEV and FIRST EPSS. LogPulse processes new CVEs every hour.
We build every detection with great care, but no two environments are the same. Log sources, parsing and configuration differ, so test a detection in your own environment before you rely on it.