Skip to navigation

Threat reportVulnerabilityTL-2026-6349

Unauthenticated RCE in NGINX HTTP/2: CVE-2026-123633 (use-after-free) and CVE-2026-123007 (send_window integer underflow)

criticalPATCHED

Wiz Research disclosed two critical HTTP/2 vulnerabilities in NGINX Open Source and NGINX Plus that allow unauthenticated remote code execution, coordinated with F5's November 18, 2026 security release. Wiz built lab PoCs but has withheld them; no in-the-wild exploitation has been reported.

Key facts

IdentifiersTL-2026-6349, CVE-2026-123633, CVE-2026-123007
SeverityCRITICAL
CVSS9.2
First disclosed
Affected productsF5 NGINX Open Source; F5 NGINX Plus
Weaknesses (CWE)CWE-416, CWE-191, CWE-787
ToolsRapid7
MITRE ATT&CK techniquesT1059 Command and Scripting Interpreter, T1059.004 Unix Shell, T1190 Exploit Public-Facing Application, T1499.002 Endpoint Denial of Service: Service Exhaustion Flood, T1499.004 Application or System Exploitation
MotivationUNKNOWN
Target sectorstechnology, cloud, telecoms, finance, government administration, health, retail
Target regionsGlobal
Detection rules9 (1 shown free)
Sources8 cited sources

Detection coverage

As of 2026-11-18, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-6349 across Splunk SPL, Microsoft KQL and Sigma, covering 21 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: NGINX Process Spawning Unix Shell (Post-Exploitation of CVE-2026-123633 / CVE-2026-123007)

Detects a shell (sh, bash, dash, zsh, ash, ksh) whose parent is the nginx binary using Sysmon for Linux process-creation events. Wiz lists commands launched by NGINX as a post-exploitation warning sign for the unauthenticated RCE in the HTTP/2 stack. A web server worker should not normally fork interactive or command shells.

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1059, T1059.004, T1190
  • Data sources: sysmon:linux (index=linux), Sysmon for Linux EventCode 1
  • Severity: critical
  • Confidence: high

Splunk SPL

index=linux sourcetype="sysmon:linux" EventCode=1 earliest=-24h ParentImage="*/nginx" (Image="*/sh" OR Image="*/bash" OR Image="*/dash" OR Image="*/zsh" OR Image="*/ash" OR Image="*/ksh") | stats count min(_time) AS first_seen max(_time) AS last_seen values(CommandLine) AS commands values(ParentCommandLine) AS parent_cmd BY host User Image | convert ctime(first_seen) ctime(last_seen)

Microsoft KQL

DeviceProcessEvents
| where Timestamp > ago(24h)
| where InitiatingProcessFileName =~ "nginx"
| where FileName in~ ("sh", "bash", "dash", "zsh", "ash", "ksh")
| project Timestamp, DeviceName, AccountName, FileName, ProcessCommandLine, InitiatingProcessCommandLine, InitiatingProcessParentFileName

Sigma

title: Shell Spawned by NGINX Process (CVE-2026-123633 / CVE-2026-123007)
id: 2b8e4f7a-91c3-4d65-a0e8-5c7d3f9b1a22
status: experimental
description: Detects a Unix shell launched directly by an nginx process, a post-exploitation sign for unauthenticated RCE in NGINX HTTP/2 handling.
references:
  - https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities
author: Threadlinqs Team
date: 2026-11-18
tags:
  - attack.execution
  - attack.t1059
  - attack.t1059.004
  - attack.initial-access
  - attack.t1190
  - cve.2026-123633
  - cve.2026-123007
logsource:
  category: process_creation
  product: linux
detection:
  selection:
    ParentImage|endswith: '/nginx'
    Image|endswith:
      - '/sh'
      - '/bash'
      - '/dash'
      - '/zsh'
      - '/ash'
      - '/ksh'
  condition: selection
falsepositives:
  - Custom init or log-rotation hooks invoked by the nginx master process
  - Admin scripts run via nginx exec modules
level: high

Known false positives:

  • Legitimate nginx-launched helper scripts such as logrotate postrotate or binary-upgrade hooks
  • Operator troubleshooting that runs commands through an nginx exec module

Tuning notes: Allowlist known helper scripts by CommandLine for the nginx master process (not workers). Ensure Sysmon for Linux or auditd execve telemetry is deployed on every NGINX host and containers. Keep parent matching on '/nginx' to include both OSS and Plus builds.

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)
  • Long-Lived High-Volume HTTP/2 Session on [indicator] (CVE-2026-123007 WINDOW_UPDATE Abuse) · unlock with TL Creds
  • [indicator] Process Dropping Files in Temp or Shared-Memory Paths (Payload Staging after CVE-2026-123633 / CVE-2026-123007) · unlock with TL Creds
  • [indicator] Worker Crash Followed by Child Process Within 30 Minutes (CVE-2026-123633 / CVE-2026-123007 Exploit Chain) · unlock with TL Creds
  • NGINX-Spawned Shell Download-and-Execute Command Line (Post-Exploitation of CVE-2026-123633 / CVE-2026-123007) · unlock with TL Creds
  • NGINX-Spawned Reverse Shell One-Liner (CVE-2026-123633 / CVE-2026-123007 Post-Exploitation) · unlock with TL Creds
  • [indicator] Connection-Slot Exhaustion Burst (CVE-2026-123633 Trigger Precondition) · unlock with TL Creds
  • [indicator] Worker Process Crash Burst on Fatal Signal (CVE-2026-123633 / CVE-2026-123007 Exploitation) · unlock with TL Creds
  • [indicator] Process Initiating Outbound Connection to Public IP (Possible Reverse Shell / Callback after CVE-2026-123633 / CVE-2026-123007) · unlock with TL Creds

Indicators of compromise

As of 2026-11-18, Threadlinqs Intelligence tracks 21 indicators of compromise for TL-2026-6349.

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

Technical analysis

CVE-2026-123633 is an HTTP/2 connection use-after-free. A connection that is waiting for the rest of a HEADERS frame is marked reusable even though it has no active requests. ngx_http_v2_create_stream() increments h2c->processing but does not remove the connection from the reusable list. When free connection slots run low, ngx_drain_connections() can close that connection mid-request. If creating the GOAWAY frame then fails (for example at the internal frame limit), the error path frees the connection's memory while the request is still using it. The condition is most relevant when NGINX runs as a reverse proxy under connection-slot pressure. It affects NGINX OSS from 1.19.7 through 1.31.8 and NGINX Plus from R33 / 37.0.0. Fixes: OSS 1.30.7 (stable) and 1.31.9 (mainline); Plus 37.0.7.1 and 37.2.0.1.

CVE-2026-123007 is an HTTP/2 send_window integer underflow (memory corruption in HTTP/2 flow control). ngx_http_v2_filter_cleanup() returns unused window credit to h2c->send_window without checking the HTTP/2 maximum, so the counter can exceed the limit. The bounds check in ngx_http_v2_state_window_update() then underflows as an unsigned subtraction and wrongly permits further increases. The oversized value is converted to off_t in ngx_http_v2_send_chain() and becomes negative, and ngx_ssl_send_chain() then performs an out-of-bounds memory copy. This bug is reachable when NGINX serves content directly, not only as a proxy. Wiz demonstrated it over HTTPS on 64-bit systems with official 1.31.7 and 1.31.8 builds serving static files. Exploitation requires sending a large number of WINDOW_UPDATE frames. It affects OSS from 1.9.5 (2015) through 1.31.8 and Plus from R33 / 37.0.0. Fixes: OSS 1.30.7 and 1.31.9; Plus 37.0.8.1 and 37.3.0.1.

Both issues require HTTP/2 to be enabled and are described by Wiz as unauthenticated remote code execution. ASLR does not stop either bug, because the primitives can be used to read memory first. A CDN or WAF that terminates HTTP/2 in front of NGINX may block parts of the exploit. Wiz states that it has lab proofs of concept and is not releasing them. The article reports no in-the-wild exploitation and publishes no IOCs. Wiz and F5 give a shared CVSS 4.0 score of 9.2 (Critical) without a vector string; nginx.org lists the issues with its own severity labels (medium for CVE-2026-123633, major for CVE-2026-123007). The bugs were also found independently by Ikotas Labs, Metnir, Rapid7 and Xint. Wiz credits its Atlas harness for finding them.

Defenders should upgrade, or as an interim measure set 'http2 off;' (NGINX 1.25.1+) and remove the http2 parameter from listen directives. Wiz's detection guidance is general: investigate unexpected NGINX worker crashes and commands launched by NGINX (warning signs, not confirmed indicators), and watch for long-lived HTTP/2 connections sending large volumes of data, which may indicate CVE-2026-123007 activity.

MITRE ATT&CK techniques by tactic:

Execution

T1059 Command and Scripting Interpreter; T1059.004 Unix Shell

Initial Access

T1190 Exploit Public-Facing Application

Impact

T1499.002 Endpoint Denial of Service: Service Exhaustion Flood; T1499.004 Application or System Exploitation

Remediation

Patches

  • F5 advisory K000163928 (CVE-2026-123633)
  • F5 advisory K000163926 (CVE-2026-123007)

Immediate actions

  • Upgrade NGINX Open Source to 1.30.7 (stable) or 1.31.9 (mainline)
  • Upgrade NGINX Plus to 37.0.7.1 / 37.2.0.1 (CVE-2026-123633) and 37.0.8.1 / 37.3.0.1 (CVE-2026-123007)
  • Where patching is delayed, set 'http2 off;' in affected server blocks (NGINX 1.25.1+) and remove the http2 parameter from listen directives

Workarounds

  • Disable HTTP/2, test compatibility, reload NGINX and confirm old workers have exited; re-enable after upgrading
  • Terminate HTTP/2 at a CDN or WAF in front of NGINX, which may block parts of the exploit

Longer-term hardening

  • Inventory all internet-facing NGINX instances, including reverse proxies, ingress controllers and container images
  • Alert on NGINX worker crashes and on child processes spawned by NGINX workers
  • Baseline HTTP/2 connection duration and data volume to spot long-lived, high-volume HTTP/2 sessions

Affected and fixed versions

  • F5 — NGINX Open Source
    Vulnerable versions: 1.19.7-1.31.8 (CVE-2026-123633); 1.9.5-1.31.8 (CVE-2026-123007)
    Fixed in: 1.30.7 (stable); 1.31.9 (mainline)
  • F5 — 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)

Timeline

Last updated · 2 updates · revalidated 2× · latest source

  • NGINX 1.9.5, the first release containing HTTP/2 support affected by CVE-2026-123007, ships in 2015 (exact day not stated in sources).
  • Wiz reports the HTTP/2 use-after-free (CVE-2026-123633) to F5; F5 says another team had already reported it.
  • F5 provides a patch for CVE-2026-123633 to Wiz for review.
  • Rapid7 makes initial outreach to F5 about the NGINX HTTP/2 flow-control flaw (CVE-2026-123007), independent of Wiz.
  • F5 confirms outreach and Rapid7 discloses the vulnerability details to F5.
  • F5 validates the Rapid7 report, assigns CVE-2026-123007 and sets the public disclosure date.
  • Wiz reports the send_window integer underflow to F5.
  • F5 confirms the second report matches CVE-2026-123007 and includes it in the November 18 release.
  • Rapid7 (Stephen Fewer, sfewer-r7) publishes a simple-trigger PoC and an unauthenticated RCE PoC against a linux/amd64 Docker nginx 1.31.8 image; no in-the-wild exploitation reported.
  • NVD publishes CVE-2026-123633 and CVE-2026-123007 (status Received; CVSS 4.0 9.2, CVSS 3.1 8.1).
  • F5 security release (OSS 1.30.7 / 1.31.9, Plus fixes) and coordinated public disclosure; Wiz publishes its analysis and withholds PoCs.

Update history

Sources cited

Drafted by the Threadlinqs research pipeline from 8 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