Skip to navigation

Threat reportVulnerabilityTL-2026-6514

NGINX HTTP/2 RCE Flaws CVE-2026-123633 and CVE-2026-123007 ("nginx2root" Unauthenticated Remote Code Execution)

criticalPATCHED

F5/NGINX patched two HTTP/2 memory-corruption flaws, a use-after-free (CVE-2026-123633) and a flow-control integer underflow (CVE-2026-123007), that can let unauthenticated remote attackers execute code as the nginx worker on servers with HTTP/2 enabled. Wiz Research confirmed code execution with an ASLR bypass on official 1.31.7/1.31.8 builds and Rapid7 has published a constrained PoC for CVE-2026-123007; no in-the-wild exploitation has been reported and neither CVE is in CISA KEV as of 2026-11-19.

Key facts

IdentifiersTL-2026-6514, CVE-2026-123633, CVE-2026-123007
Also known asnginx2root, Drainbreak (Metnir name for CVE-2026-123633)
SeverityCRITICAL
CVSS9.2 (CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N)
First disclosed
Exploitation statusPublic proof-of-concept exploit for a linked CVE
Affected productsF5 / NGINX NGINX Open Source (CVE-2026-123633, HTTP/2 use-after-free); F5 / NGINX NGINX Open Source (CVE-2026-123007, HTTP/2 flow-control underflow); F5 / NGINX NGINX Plus; Kubernetes community ingress-nginx (retired)
Weaknesses (CWE)CWE-416, CWE-191, CWE-787
ToolsRapid7, Wiz Atlas
MITRE ATT&CK techniquesT1059.004 Unix Shell, T1068 Exploitation for Privilege Escalation, T1190 Exploit Public-Facing Application, T1499.004 Endpoint Denial of Service: Application or System Exploitation, T1611 Escape to Host
MotivationUNKNOWN
Target sectorstechnology, telecoms, finance, government administration, health, education, retail
Target regionsGlobal
Detection rules9 (1 shown free)
Sources14 cited sources

Detection coverage

As of 2026-11-20, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-6514 across Splunk SPL, Microsoft KQL and Sigma, covering 14 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: Shell Spawned by NGINX Worker UID (auditd) — nginx2root Post-Exploitation

Detects /bin/sh, bash, dash or similar executed under the nginx worker UID using the auditd execve rule recommended by Xint (key nginx_worker_exec). A shell spawned by an nginx worker is the clearest sign of successful code execution via CVE-2026-123007 or CVE-2026-123633.

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1059.004, T1190
  • Data sources: linux auditd (index=linux, sourcetype=linux:audit), linux_syslog (Sentinel Syslog table with AMA auditd)
  • Severity: critical
  • Confidence: high

Splunk SPL

index=linux sourcetype=linux:audit earliest=-24h "nginx_worker_exec" type=SYSCALL | rex field=_raw "\bexe=\x22(?<exe>[^\x22]+)\x22" | rex field=_raw "\beuid=(?<euid>\d+)" | where match(exe,"/(sh|bash|dash|ash|zsh|ksh)$") | stats count min(_time) as first_seen max(_time) as last_seen values(exe) as shells by host, euid | convert ctime(first_seen) ctime(last_seen)

Microsoft KQL

Syslog | where TimeGenerated > ago(24h) | where SyslogMessage has "nginx_worker_exec" | where SyslogMessage matches regex @"exe=""(/usr)?/bin/(sh|bash|dash|ash|zsh|ksh)""" | summarize Events = count(), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated) by Computer | project Computer, Events, FirstSeen, LastSeen

Sigma

title: Shell Executed by NGINX Worker UID via auditd (nginx2root)
id: 2b9d4e18-5a7c-4f63-8e02-91c4d6a7f302
status: experimental
description: Detects a shell executed under the nginx worker UID, recorded by the auditd rule 'auditctl -a always,exit -F arch=b64 -S execve,execveat -F euid=NGINX_UID -k nginx_worker_exec'. Indicates likely successful exploitation of CVE-2026-123007 or CVE-2026-123633.
references:
    - https://xint.io/blog/nginx2root-remote-code-execution
    - https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities
author: Threadlinqs Team
date: 2026/11/19
tags:
    - attack.execution
    - attack.t1059.004
    - attack.initial-access
    - attack.t1190
    - cve.2026.123007
    - cve.2026.123633
logsource:
    product: linux
    service: auditd
detection:
    selection:
        type: 'SYSCALL'
        key: 'nginx_worker_exec'
        exe|endswith:
            - '/sh'
            - '/bash'
            - '/dash'
            - '/ash'
            - '/zsh'
            - '/ksh'
    condition: selection
falsepositives:
    - Administrators running nginx with a custom wrapper script that execs a shell
    - Misconfigured auditd rule that matches the nginx master (root) rather than the worker UID
level: critical

Known false positives:

  • Custom nginx deployments that invoke shell scripts from the worker (e.g. fcgiwrap/CGI wrappers running as the worker UID)
  • Audit rule scoped to euid=0 rather than the worker UID, which would also match legitimate master-process activity

Tuning notes: Requires the auditd rule 'auditctl -a always,exit -F arch=b64 -S execve,execveat -F euid=<nginx worker uid> -k nginx_worker_exec' (events are recorded only after installation). Substitute the real worker UID. Exclude known CGI wrapper binaries by exe path if they are legitimate. Confirm the Sentinel Syslog collection includes the auditd facility.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple and Gold in full, 2 calls a day on a free account)
  • Long-Lived Heavy-Inbound TLS Flow or Single-Source Short-Connection Burst to HTTPS — CVE-2026-123007 HTTP/2 Window-Underflow Exploitation Traffic · unlock with TL Creds
  • NGINX Worker Spawning Download Tools, Interpreters or Reverse-Shell Commands · unlock with TL Creds
  • Root or Container-Escape Activity in NGINX Process Lineage — nginx2root Privilege Escalation · unlock with TL Creds
  • CVE-2026-123007 Public PoC Tooling Execution (Rapid7 exploit.py / [indicator]) · unlock with TL Creds
  • Shell Process with NGINX as Parent (Process Creation) — nginx2root Code Execution · unlock with TL Creds
  • Outbound Connection to Public IP from Shell or Tool Running as Web Worker UID · unlock with TL Creds
  • NGINX Worker Crash / Connection Exhaustion Burst — CVE-2026-123007 & CVE-2026-123633 (nginx2root) Exploitation Attempt · unlock with TL Creds
  • SCTP Socket Created by NGINX Process — Worker-to-Root Kernel Chain Indicator · unlock with TL Creds

Indicators of compromise

As of 2026-11-20, Threadlinqs Intelligence tracks 14 indicators of compromise for TL-2026-6514.

Sample indicators (1 of 14)

  • URL: hxxps://github[.]com/sfewer-r7/CVE-2026-123007

Defanged, TLP:CLEAR. Full set of 14 indicators: unlock with TL Creds.

14 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

On 2026-11-18 F5 released NGINX Open Source 1.30.7 (stable) and 1.31.9 (mainline), plus NGINX Plus 37.0.7.1/37.0.8.1 and 37.2.0.1/37.3.0.1, fixing ten security issues including two HTTP/2 flaws scored CVSS 4.0 9.2 (CVSS 3.1 8.1 per F5 CNA records as reported by secondary sources). CVE-2026-123633 is a use-after-free (CWE-416 per Equixly) affecting NGINX 1.19.7-1.31.8: an HTTP/2 connection paused mid-HEADERS is marked reusable and stays on the reusable-connection list after the request starts. When worker connection slots run low during upstream proxying (proxy_pass, fastcgi_pass, grpc_pass), ngx_drain_connections() can close that connection and free memory the request still uses; Wiz also describes a second route where GOAWAY frame construction fails and the error path frees the connection. Proxy configurations are the highest risk.

CVE-2026-123007 (nicknamed nginx2root; CWE-191 and CWE-787 per F5/Rapid7/Equixly; CVSS 4.0 vector CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N per Rapid7) affects every release from 1.9.5 (2015, first HTTP/2 release) through 1.31.8. When a stream is cancelled, ngx_http_v2_filter_cleanup() refunds unsent DATA credit to h2c->send_window without checking the HTTP/2 maximum (2^31-1). A client that already restored the same credit with WINDOW_UPDATE can push the window past the maximum; the unsigned size_t bounds check wraps, the window is later cast to a signed off_t producing a negative length, and the TLS send path (ngx_ssl_send_chain) performs a memcpy with an enormous length. On x86-64 glibc the copy terminates after limited out-of-bounds reads and writes, giving heap read/write primitives. Code runs with the nginx worker's privileges. Wiz states attackers must leak memory addresses and groom the heap, and confirmed code execution with an ASLR bypass on official 1.31.7 and 1.31.8 builds serving static content over HTTPS on 64-bit systems.

Five teams independently reported the HTTP/2 flaws (Wiz Research, Ikotas Labs, Metnir, Rapid7, Xint); sources disagree on which team found which bug. Xint chained nginx flaws with a separate unpatched Linux SCTP kernel bug (Linux 4.15+, no CVE named) to get root, including out of a Docker container. Rapid7's public PoC (github.com/sfewer-r7/CVE-2026-123007) targets a fresh linux/amd64 Docker container running nginx 1.31.8 with HTTP/2+TLS, needs roughly 128 GB of HTTP/2 traffic on a single connection (about 2 minutes at 10 Gbit/s, about 17 minutes at 1 Gbit/s, impractical below about 300 Mbit/s because of nginx's default one-hour connection lifetime), depends on the glibc AVX512 memcpy path, and is documented as unreliable against long-running workers, concurrent clients, or proxies that alter HTTP/2 frames. Wiz and Xint are withholding working exploits. CDNs/WAFs that terminate HTTP/2 may break parts of an attack, but origins reachable directly remain exposed. Disabling HTTP/2 mitigates only these two CVEs; the same release fixes CVE-2026-123634 (resolver), CVE-2026-121810 (HTTP/3) and CVE-2026-113425 (mail proxy) that are not mitigated by that workaround.

Exposure is broad: Xint's Shodan snapshot (2026-11-10) found 56.7M nginx hosts with 98.9% of version-reporting hosts in range for CVE-2026-123007, and Censys counted about 8.8M services on an affected version with HTTP/2 enabled on 2026-11-19. Downstream impact includes Ubuntu (USN-9159-1), Debian, Alpine, Amazon Linux, AlmaLinux, Synology (SA-26:20) and the retired community ingress-nginx. Detection is difficult because WINDOW_UPDATE and RST_STREAM control frames are not logged as requests; defenders should watch for nginx worker crashes (signal 11), shells spawned by the worker UID, and long-lived HTTP/2 connections with heavy inbound bytes but few logged requests.

MITRE ATT&CK techniques by tactic:

Execution

T1059.004 Unix Shell

Privilege Escalation

T1068 Exploitation for Privilege Escalation; T1611 Escape to Host

Initial Access

T1190 Exploit Public-Facing Application

Impact

T1499.004 Endpoint Denial of Service: Application or System Exploitation

Remediation

Patches

  • NGINX Open Source 1.30.7 and 1.31.9 (released 2026-11-18)
  • NGINX Plus 37.0.7.1 / 37.2.0.1 (CVE-2026-123633) and 37.0.8.1 / 37.3.0.1 (CVE-2026-123007)
  • Ubuntu USN-9159-1 (24.04 1.24.0-2ubuntu7.20; 22.04 1.18.0-6ubuntu14.23; 26.04 1.28.3-2ubuntu1.13; 26.10 1.30.4-7ubuntu1.2)
  • Alpine nginx 1.30.7-r0 (3.24/edge); Amazon Linux ALAS2023-2026-3494

Immediate actions

  • Upgrade NGINX Open Source to 1.30.7 (stable) or 1.31.9 (mainline) and fully restart nginx (a reload is not sufficient); confirm old workers have exited
  • If patching is delayed, set 'http2 off;' in each affected server block on nginx 1.25.1+ and remove the 'http2' parameter from listen directives (on 1.9.5-1.25.0 remove 'http2' from 'listen 443 ssl http2;'), then reload and confirm old workers exited
  • Verify exposure with 'nginx -V 2>&1 | grep http_v2_module', 'nginx -T' and 'openssl s_client -alpn h2' against origins (including origins behind a CDN)
  • Enable auditd execve monitoring for the nginx worker UID and alert on /bin/sh or /bin/bash spawned by workers

Workarounds

  • Disable HTTP/2 on all listeners (stops only CVE-2026-123633 and CVE-2026-123007; clients needing HTTP/2 such as native gRPC will break)
  • Community ingress-nginx (retired, last release v1.15.1) will not be patched: set use-http2: "false" in the ConfigMap or migrate to a maintained controller

Longer-term hardening

  • Run nginx workers as an unprivileged user in hardened containers and restrict outbound connections from web tier hosts
  • Block the SCTP kernel module where unused (install sctp /bin/false in /etc/modprobe.d/) to reduce the documented worker-to-root chain
  • Add per-connection HTTP/2 logging ($connection, $connection_requests, $request_length) and alert on long-lived connections with large inbound byte counts and few requests
  • Track distro packages (Ubuntu, Debian, RHEL, Alpine, Amazon Linux, AlmaLinux) and downstream appliances (Synology) for backported fixes

Affected and fixed versions

  • F5 / NGINX — NGINX Open Source (CVE-2026-123633, HTTP/2 use-after-free)
    Vulnerable versions: 1.19.7 - 1.31.8
    Fixed in: 1.30.7; 1.31.9
  • F5 / NGINX — NGINX Open Source (CVE-2026-123007, HTTP/2 flow-control underflow)
    Vulnerable versions: 1.9.5 - 1.31.8
    Fixed in: 1.30.7; 1.31.9
  • F5 / NGINX — NGINX Plus
    Vulnerable versions: R33 and 37.0.0 onward
    Fixed in: 37.0.7.1; 37.2.0.1 (CVE-2026-123633); 37.0.8.1; 37.3.0.1 (CVE-2026-123007)
  • Kubernetes community — ingress-nginx (retired)
    Vulnerable versions: v1.15.1 (bundles nginx 1.27.1, use-http2 on by default)

Timeline

Last updated · revalidated 1× · latest source

  • NGINX 1.9.5, the first release with HTTP/2 support, ships the flow-control accounting code later tracked as CVE-2026-123007.
  • Xint researchers find the nginx2root flaws (per Xint timeline); Metnir separately claims it found CVE-2026-123633 on 2026-08-29 and reported it 2026-09-12.
  • Xint reports the findings to F5 via HackerOne; validation completes 2026-10-20 and reports reach F5's nginx team 2026-10-27.
  • Wiz Research reports the HTTP/2 use-after-free (CVE-2026-123633) with a proposed fix and an ASLR-bypassing exploit; F5 says another team had already reported it.
  • F5 shares a patch for CVE-2026-123633 with Wiz for review; Xint validates patches.
  • Wiz reports the HTTP/2 flow-control flaw; F5 assigns CVE-2026-123007 and confirms on 2026-11-17 that it will be fixed in the 2026-11-18 release.
  • CERT-FR issues alert CERTFR-2026-ALE-017 and advisory CERTFR-2026-AVI-1567, noting a public PoC and recommending disabling HTTP/2 until patched.
  • F5 releases NGINX 1.30.7 and 1.31.9 and NGINX Plus fixes; Wiz, Xint, Rapid7 and others disclose; Rapid7 publishes a constrained PoC for CVE-2026-123007.
  • Ubuntu publishes USN-9159-1; Censys still counts about 8.8M services on an affected version with HTTP/2 enabled; no in-the-wild exploitation reported and not in CISA KEV.
  • NVD records for both CVEs are modified with F5 CVSS 4.0 9.2 / CVSS 3.1 8.1 scoring, CWE-191/787 and CWE-416.

Update history

Sources cited

Other reports on CVE-2026-123633

Other reports on CVE-2026-123007

Previous and next in vulnerability

Drafted by the Threadlinqs research pipeline from 14 sources; published ; last updated .

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats