CVE-2026-123007 · CVE-2026-123633

Disable HTTP/2 on affected listeners.

For NGINX 1.25.1 and later, remove the legacy http2 listen parameter and set http2 off; in each affected server block. For 1.9.5–1.25.0, remove http2 from the listen directive. Check every server sharing the address and port.

NGINX 1.25.1+ · illustrative server block
listen 443 ssl;
http2 off;
Legacy listen syntax · remove HTTP/2
listen 443 ssl;

Run nginx -t, reload, and verify direct-to-origin protocol negotiation. A CDN may answer HTTP/2 while the origin is HTTP/1.1, or the reverse.

Compatibility impact

Native gRPC and clients that require HTTP/2 can stop working. This control does not address the resolver, HTTP/3 or mail proxy CVEs.

CVE-2026-123634

Remove affected request-time DNS resolution.

Xint demonstrated this path with a resolver, a request-derived proxy_pass destination, and concurrent mirror subrequests. Prefer a fixed upstream group where the application can support it. Removing mirroring alone is insufficient because other subrequests may reach the bug.

Review all resolver and variable-based upstream configurations. A static upstream changes routing behavior, so test backend selection before rollout.

CVE-2026-121810

Disable affected HTTP/3/QUIC listeners.

For configurations proxying HTTP/3 to an upstream, remove QUIC listen directives and stop advertising HTTP/3 while patching. Keep your normal TLS/TCP listener. Validate with nginx -t and check UDP listeners after reload.

Illustrative HTTP/3 response change
listen 443 ssl;
http3 off;
add_header Alt-Svc "clear" always;
CVE-2026-113425

Restrict affected mail proxy access.

If NGINX mail uses both proxy on and auth_http, allow only trusted clients while patching. Binding to loopback is viable only when remote mail clients are not needed. Test IMAP, POP3 and SMTP delivery after the change.

SEPARATE LINUX ISSUE

Assess the SCTP escalation separately.

Xint demonstrated host-root escalation by chaining an unpatched SCTP kernel flaw after obtaining worker code execution. On hosts that do not need SCTP, their research suggests blocking module loading; this does not affect an already loaded or built-in SCTP implementation. Follow the kernel vendor's fix and your host change procedure.

Xint's original mitigation and kernel notes

Return to patching