Konfirmity
All security advisories

//security advisory

nginx2root (CVE-2026-123007): NGINX Security Advisory

nginx2root is a group of five vulnerabilities in NGINX and a separate Linux kernel privilege escalation reported by Xint. CVE-2026-123007, the broadest of the five NGINX flaws, can let an unauthenticated attacker run code as an NGINX worker when HTTP/2 is enabled. Upgrade NGINX Open Source to 1.30.7 stable or 1.31.9 mainline, or apply the fixed NGINX Plus or vendor build. Replace the running process and confirm the update on every replica.

On this page
  1. Are you affected?
  2. What to do
  3. Fixed versions
  4. Check your deployment
  5. Until you patch
  6. The five NGINX flaws
  7. Signs of compromise
  8. Timeline
  9. Recording it for compliance
  10. FAQ
  11. Sources

Are you affected?

Check which NGINX build is running and which features are enabled. Start with public HTTP/2 listeners, then review ingress, HTTP/3, resolver and mail proxy configurations.

  • You serve HTTP/2 on a public NGINX listener

    An unpatched NGINX server, including sites serving static files

    Act now

    Patch this deployment first. If the update must wait, disable HTTP/2 where compatible or restrict access. Until you patch

  • NGINX handles HTTP/3, DNS resolution or mail proxying

    Other CVEs in the same release depend on these configurations

    Update needed

    Review affected listeners and proxy routes. Upgrade to a build that covers all five CVEs. Affected configurations

  • You use an ingress controller or managed gateway

    Packaged, containerized or provider-managed NGINX

    Update needed

    Identify the serving image or ask the provider for the fixed build. For deployments you manage, roll out the update to every replica. Fixed versions

  • You serve HTTP/1.x only

    Web listeners only, with static files or fixed upstream addresses

    Low risk

    Confirm the active configuration across every listener and include. Review resolver and mail proxy settings separately if you use them. Check your deployment

What to do

Apply the fix for your release track, replace the running NGINX process and verify the update on every replica.

  1. Inventory every NGINX instance that processes traffic

    Start with public web servers, reverse proxies, ingress controllers and mail proxies. Include internal instances that accept traffic from less trusted networks. Record who owns each instance, its running binary, its package or image source and which protocols reach it.
  2. Install a fixed build and replace the running executable

    Restart NGINX or complete a supported live binary upgrade. A configuration reload keeps the existing master executable. For containers or ingress, roll out the fixed image to every serving pod or container.
  3. Verify every replica and review earlier exposure

    Confirm the running build, that old workers have exited and that health and protocol checks pass. Review process and network logs on systems that were exposed.

Fixed versions

NGINX published fixes for all five NGINX CVEs on 18 November 2026. Compare your deployment with the fixed version for its product and release track. NGINX release announcement.

DeploymentFixed version or upgrade target
NGINX Open Source1.30.7 stable or 1.31.9 mainline. Older upstream branches should move to a supported fixed release.
NGINX PlusPLS.37.0.8.1 LTS or PLS.37.3.0.1 continuous release. The October Plus builds PLS.37.0.7.1 and PLS.37.2.0.1 already fixed CVE-2026-123633. Upgrade again for the other four.
F5 NGINX Ingress Controller5.8.0 bundles NGINX Open Source 1.31.9 or NGINX Plus PLS.37.3.0.1. The 2026-lts-r11 controller bundles NGINX Plus PLS.37.0.8.1.
Distribution, container or applianceUse an image, package or appliance release whose vendor documents the applicable CVE fixes. Check the full package revision or image digest and the build actually deployed.

Distribution backports can leave the version printed by nginx -vlooking old. Compare the full installed package revision with your distribution's security tracker. No fixed CVE-2026-123007 package was verified in the Ubuntu, Debian, Red Hat or SUSE records available for this review. Xint guidance on backported fixes.

F5's release numbers apply to its own controller. If you use community ingress-nginx, Kubernetes ended security maintenance in March 2026. Identify the image actually deployed, restrict exposure as needed and move to a maintained controller. For a managed gateway or appliance, ask the provider which build contains the fixes. F5 controller releases · F5 controller LTS releases · Kubernetes retirement notice.

Check your deployment

Check the HTTP/2 and HTTP/3 build options and review the configuration for HTTP/2 directives, QUIC listeners, proxy and resolver settings, and mail blocks. Inspect generated includes locally. The on-disk configuration may differ from what existing workers loaded. Check your origin from an authorized network as well as the CDN endpoint.

Inspect the NGINX binary and test TLS ALPN on your own listener
nginx -v
nginx -V
openssl s_client -connect HOST:443 -servername HOST -alpn h2 </dev/null

Run the version checks against the service's binary and compare with its package or image provenance. Replace HOST with the hostname of your listener. A completed handshake with ALPN protocol: h2 confirms HTTP/2 negotiation at that endpoint. A failed handshake is inconclusive, and ALPN covers TLS listeners only. Xint exposure checks · NGINX process control.

Until you patch

If a fixed build cannot be deployed immediately, use the temporary controls that match your configuration. Validate with nginx -t, reload through your service manager and verify the listeners and old workers. A restart or controlled rollout can close old sessions if they keep serving the prior configuration. Xint mitigation guidance.

CVETemporary risk reduction
CVE-2026-123007 and CVE-2026-123633Disable HTTP/2 on each affected server block. Starting with NGINX 1.25.1, use http2 off and remove the legacy http2 argument from listen directives. On older releases, remove that listen argument. Review every server block sharing an address and port. If native gRPC requires HTTP/2, prioritize a patch or restrict access while it is pending.
CVE-2026-123634Replace request-time DNS lookups on affected proxy routes with fixed upstream groups where practical. Review both primary and subrequest locations. Disabling mirroring alone leaves other subrequest sources, including SSI, to assess.
CVE-2026-121810Disable HTTP/3, remove affected QUIC listeners, stop advertising HTTP/3 and verify the affected UDP port is closed. Keep the ordinary HTTPS listener over TCP where needed.
CVE-2026-113425Restrict access to affected mail proxy listeners to trusted clients, or take them out of service until patched. Check IPv4 and IPv6 exposure.

Linux SCTP and container hosts

Xint demonstrated host root access from an NGINX container by using a separate Linux kernel SCTP flaw after compromising the worker. The NGINX packages address the five NGINX vulnerabilities. No public CVE or fixed kernel was verified for Xint's separate finding on 18 November. Check host and Kubernetes node images with your kernel provider. If SCTP is unnecessary, ask the platform owner about disabling it after checking workload dependencies and whether it is loaded as a module or built into the kernel. Xint kernel findings.

The five NGINX flaws

CVE-2026-123007 is a memory-corruption flaw in how NGINX manages HTTP/2 flow control. It can crash a worker or allow unauthenticated remote code execution with the worker's permissions. Xint and Wiz demonstrated code execution in their tests. F5 identifies disabled or bypassed address space layout randomization (ASLR) as a condition for code execution. Wiz demonstrated that a static site with HTTP/2 enabled can be affected. F5 CNA record · Wiz Research.

Upstream Open Source first affected versions and configuration to review
CVEFirst affectedConfiguration to review
CVE-2026-1230071.9.5HTTP/2 enabled on a client-facing listener, including NGINX serving static files.
CVE-2026-1236331.19.7NGINX accepts HTTP/2 and proxies requests to a backend. F5 identifies low worker connection availability as a condition.
CVE-2026-1236340.6.18NGINX performs request-time DNS resolution for a variable proxy destination, with mirror or SSI subrequests resolving the same name.
CVE-2026-1218101.25.0HTTP/3 enabled. Prioritize services that accept QUIC and proxy to a backend.
CVE-2026-1134250.5.33NGINX configured as a mail proxy. Review IMAP, POP3 and SMTP listeners that use HTTP authentication.

Where the sources differ

The affected upstream releases run through 1.30.6 on the stable track and 1.31.8 on mainline. For the resolver flaw, NGINX lists 0.6.18 as the first affected release, while Xint dates its tested mirror configuration to 1.13.4. For the mail proxy, NGINX and F5 list 0.5.33 and Xint lists 0.5.15. If you still operate an older mail proxy, move to a supported, patched build. NGINX advisories · Xint disclosure.

Signs of compromise

CISA's assessment of CVE-2026-123007 recorded exploitation as none at 16:04 UTC on 18 November 2026. Xint, Wiz and Rapid7 demonstrated code execution under test conditions. Use access logs alongside host telemetry because HTTP/2 connection activity can occur outside the events recorded as ordinary requests. CVE record and CISA assessment · Xint investigation guidance.

  • Look for shells or other unexpected child processes launched by an NGINX worker. Check process ancestry and timing with your endpoint or Linux audit logs.
  • Correlate repeated worker crashes or core dumps with unusual connection duration, traffic volume and outbound activity. Each signal has benign explanations.
  • If activity is consistent with code execution, isolate the affected instance, preserve relevant logs and process evidence, and investigate the host or node and credentials accessible to the workload. Coordinate any secret rotation and rebuild through incident response.

Timeline

  1. 2026-10-21

    Wiz reports the HTTP/2 use-after-free later assigned CVE-2026-123633 to F5.

    Wiz disclosure timeline

  2. 2026-11-18

    NGINX publishes Open Source 1.30.7 and 1.31.9 with fixes for all five NGINX CVEs.

    NGINX advisories

  3. 2026-11-18 · 16:04 UTC

    CISA records no known exploitation of CVE-2026-123007 at the time of assessment.

    CVE record and CISA assessment

Recording it for compliance

Controls to record this event against
FrameworkControlWhat to record
ISO 27001:2022A.8.8Which deployments and CVEs you assessed, which listeners were exposed, and the vendor builds or image digests installed.
ISO 27001:2022 / SOC 2A.8.32 / CC8.1Temporary protocol or access changes, deployment dates, and when the old master and workers stopped serving.
SOC 2CC7.1How you verified the serving build on every replica and tracked any pending provider update.

File those records with your vulnerability management and change management evidence.

nginx2root and CVE-2026-123007 FAQ

What is nginx2root (CVE-2026-123007)?

nginx2root is Xint’s name for five NGINX flaws and a separate Linux kernel SCTP privilege escalation. The most widely applicable NGINX flaw, CVE-2026-123007, can allow unauthenticated remote code execution as an NGINX worker on an unpatched HTTP/2 listener. NGINX2Shell is another name used for the lead HTTP/2 finding.

Which NGINX versions fix nginx2root?

NGINX Open Source 1.30.7 stable and 1.31.9 mainline, and NGINX Plus PLS.37.0.8.1 LTS and PLS.37.3.0.1 continuous release, fix all five NGINX CVEs. Distribution builds can backport the changes. Compare the full package version with the vendor’s advisory.

Does disabling HTTP/2 mitigate nginx2root?

Disabling HTTP/2 on every affected NGINX listener mitigates CVE-2026-123007 and CVE-2026-123633 after old workers stop. The resolver, HTTP/3 and mail proxy findings need their own mitigations or the security update. Test HTTP/2-dependent services such as native gRPC before changing the configuration.

Is Kubernetes NGINX Ingress Controller affected?

Check the NGINX binary and configuration shipped in your controller image. F5 NGINX Ingress Controller 5.8.0 ships NGINX 1.31.9 or NGINX Plus PLS.37.3.0.1, and F5’s 2026-lts-r11 ships Plus PLS.37.0.8.1. The retired community ingress-nginx project has its own lifecycle. F5’s release numbers apply to F5’s controller.

Does applying the NGINX patch also fix the Linux kernel flaw?

The NGINX updates fix the five NGINX CVEs. Xint describes a separate Linux SCTP privilege escalation and demonstrated host root access from an NGINX container under test conditions. No public identifier or fixed kernel for that separate finding was verified as of 18 November 2026. Track kernel guidance with your OS, Kubernetes node or cloud provider.

Is CVE-2026-123007 being exploited in the wild?

The CISA assessment attached to the CVE record marked exploitation as none on 18 November 2026 at 16:04 UTC. Researchers demonstrated code execution in tests. Review unexpected NGINX worker child processes, repeated crashes and unusual network activity while prioritizing updates.

Sources