Zarro Technology · Security briefing
Today’s briefing focuses on newly released NGINX fixes affecting web-serving and reverse-proxy infrastructure. The 18 November advisories describe serious memory-corruption risks. Public research demonstrates exploitation in a test setting; confirmed attacks in the wild are not established by the reviewed sources.
CVE-2026-123007 (9.2), CVE-2026-123633 (9.2)
The flow-control flaw affects NGINX 1.9.5–1.31.8 where HTTP/2 is enabled on a listening port. The second flaw affects 1.19.7–1.31.8 with HTTP/2 and upstream forwarding. Both can allow unauthenticated code execution as the worker process. The verified CNA CVSS 4.0 scores are 9.2; CERT-EU quotes 8.1 under the alternative scoring assessment.
Inventory enabled HTTP/2 listeners, reverse proxies, container images and vendor-bundled NGINX. Review error logs for worker exits on signals, then correlate with process-creation and network telemetry. Crashes are low-confidence investigation leads, not proof of successful code execution. No campaign-specific IoCs are published in the cited notices, and quiet logs cannot establish that a server is clean.
Update open-source NGINX to 1.31.9 mainline or 1.30.7 stable, or a distribution package explicitly carrying these fixes. NGINX Plus uses separate branch-specific fixes: consult F5’s matrix rather than applying open-source version numbers. Rebuild and redeploy affected images, and confirm the running service has loaded the corrected package.
If patching is delayed, CERT-EU recommends disabling HTTP/2 on exposed listeners to mitigate these two flaws. Apply the configuration appropriate to your version, validate it and use your supported reload procedure. This can affect HTTP/2-dependent workloads and does not address other vulnerabilities fixed in the same release.
Sources: NGINX — affected and corrected versions · CERT-EU — prerequisites, exploitation status and mitigation · F5 — full product remediation matrix
Zarro Technology