{"id":"CVE-2026-120722","aliases":[],"summary":"BIG-IP iRule Vulnerability","published_at":"2026-11-18T15:23:26.409Z","modified_at":"2026-11-18T22:56:15.768Z","products":[{"slug":"f5-bigip","name":"F5 BIG-IP / BIG-IQ","category":"proxy"}],"rating":{"severity":"critical","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","attack_path":"internet_unauthenticated","user_interaction":false,"malicious":false},"fix_available":false,"kev":{"listed":false,"ransomware":false},"public_exploit":false,"exploits":[],"priority":12.8,"details":"Description:\n\nWhen an iRule that processes client traffic using the DNS::scrape 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). \n\n\n\n\n\nImpact:\n\n\n\nTraffic 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. In addition, the attacker may be able to perform RCE. There is no control plane exposure; this is a data plane issue only.\n\n\n\n\n\n\n\nNote: Software versions which have reached End of Technical Support (EoTS) are not evaluated.","affected_stack":[{"ecosystem":"CVE","package":"F5/BIG-IP","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"21.1.0"}]},{"type":"ECOSYSTEM","events":[{"introduced":"17.5.0"}]},{"type":"ECOSYSTEM","events":[{"introduced":"17.1.0"}]}],"provider":"cvelistv5","source":"CVE-2026-120722","relation":"self"},{"ecosystem":"CVE","package":"F5/BIG-IP Next CNF","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.4.0"}]},{"type":"ECOSYSTEM","events":[{"introduced":"2.3.0"}]},{"type":"ECOSYSTEM","events":[{"introduced":"2.2.0"}]}],"provider":"cvelistv5","source":"CVE-2026-120722","relation":"self"},{"ecosystem":"CVE","package":"F5/BIG-IP Next for Kubernetes","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.4.0"}]},{"type":"ECOSYSTEM","events":[{"introduced":"2.3.0"}]},{"type":"ECOSYSTEM","events":[{"introduced":"2.2.0"}]}],"provider":"cvelistv5","source":"CVE-2026-120722","relation":"self"}],"affected_other":[],"product_status":[],"records":[{"provider":"cvelistv5","source_id":"CVE-2026-120722","relation":"self","url":"https://www.cve.org/CVERecord?id=CVE-2026-120722","license":"CC-BY-4.0","published_at":"2026-11-18T15:23:26.409Z","modified_at":"2026-11-18T22:56:15.768Z","summary":"BIG-IP iRule Vulnerability","details":"Description:\n\nWhen an iRule that processes client traffic using the DNS::scrape 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). \n\n\n\n\n\nImpact:\n\n\n\nTraffic 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. In addition, the attacker may be able to perform RCE. There is no control plane exposure; this is a data plane issue only.\n\n\n\n\n\n\n\nNote: Software versions which have reached End of Technical Support (EoTS) are not evaluated.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","source":"CVE-2026-120722"},{"type":"CVSS_V4","score":"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","source":"CVE-2026-120722"}],"affected":[{"ecosystem":"CVE","package":"F5/BIG-IP","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"21.1.0"}]},{"type":"ECOSYSTEM","events":[{"introduced":"17.5.0"}]},{"type":"ECOSYSTEM","events":[{"introduced":"17.1.0"}]}],"provider":"cvelistv5","source":"CVE-2026-120722","relation":"self"},{"ecosystem":"CVE","package":"F5/BIG-IP Next CNF","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.4.0"}]},{"type":"ECOSYSTEM","events":[{"introduced":"2.3.0"}]},{"type":"ECOSYSTEM","events":[{"introduced":"2.2.0"}]}],"provider":"cvelistv5","source":"CVE-2026-120722","relation":"self"},{"ecosystem":"CVE","package":"F5/BIG-IP Next for Kubernetes","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.4.0"}]},{"type":"ECOSYSTEM","events":[{"introduced":"2.3.0"}]},{"type":"ECOSYSTEM","events":[{"introduced":"2.2.0"}]}],"provider":"cvelistv5","source":"CVE-2026-120722","relation":"self"}],"product_status":[],"references":[{"type":"ADVISORY","url":"https://my.f5.com/manage/s/article/K000163945"}]}],"references":[{"type":"ADVISORY","url":"https://my.f5.com/manage/s/article/K000163945"}],"sources":[{"provider":"cvelistv5","source_id":"CVE-2026-120722","url":"https://www.cve.org/CVERecord?id=CVE-2026-120722","license":"CC-BY-4.0","modified_at":"2026-11-18T22:56:15.768Z","relation":"self"}]}
