It’s explicitly exploiting the http2 flow control and neither 1.1 (the link above even suggests deactivating http2 as a temporary measure) nor –afaik– http3 (which works differently just by design principle) are affected.
I assumed we are talking about the title specifically.
Crashing your service with an exploit depending “on conditions beyond the attacker’s control. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled” that “may allow remote attackers to cause a denial-of-service (DoS) on the NGINX system or to possibly trigger a code execution” may be a critical issues, too, but is not exactly the same thing as a proven way to get root access.
Only if the next one targets http3 instead of http2 😉
this one is targeting http3 too
It’s explicitly exploiting the http2 flow control and neither 1.1 (the link above even suggests deactivating http2 as a temporary measure) nor –afaik– http3 (which works differently just by design principle) are affected.
https://www.cve.org/CVERecord?id=CVE-2026-121810
I assumed we are talking about the title specifically.
Crashing your service with an exploit depending “on conditions beyond the attacker’s control. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled” that “may allow remote attackers to cause a denial-of-service (DoS) on the NGINX system or to possibly trigger a code execution” may be a critical issues, too, but is not exactly the same thing as a proven way to get root access.