Two critical remote-code-execution vulnerabilities in NGINX HTTP/2 are disclosed as active security issues and are described as affecting servers with HTTP/2 enabled. Attackers who can reach the relevant NGINX port may be able to run code on the server without authentication. The reports identify CVE-2026-123633 as a use-after-free in the HTTP/2 request handling path, and CVE-2026-123007 as an integer underflow present since older NGINX versions.
Multiple outlets also point to mitigations and timeline details. LWN and the Hacker News note that fixes are available in specific NGINX versions released by F5, while one additional report emphasizes practical steps for auditing a fleet for HTTP/2 exposure, including checking configuration and whether HTTP/2 is implicitly enabled. LWN further reports that the vendor-linked researcher account includes a local privilege escalation kernel vulnerability tied to SCTP, which could be chained with the NGINX issue on systems where SCTP is reachable.
Overall, outlets largely agree on the unauthenticated nature of the remote issue and the requirement that HTTP/2 be enabled, while they vary in how much they focus on technical exploitation paths versus operational mitigation and incident readiness.