CVE-2026-123633
validatedZero produced an exploit or a check.GHSA-7xxj-p8w5-434q ↗EUVD-2026-128944 ↗
description
NGINX Open Source and NGINX Plus deployments acting as HTTP/2 reverse proxies are affected. A remote unauthenticated client may crash a worker process and, in environments without effective ASLR protection, may be able to execute code. Exposure depends on HTTP/2 being enabled for client connections, proxying to an upstream backend, and worker connections becoming scarce.
mitigation
Disable HTTP/2 on externally reachable NGINX listeners, such as by removing HTTP/2 listener configuration or setting http2 off;. Keep worker-connection capacity under review and obtain the vendor-supported patched package for the deployed distribution or NGINX release.
fixed in 1.31.9, 1.30.7, *, 37.2.0.1, 37.0.7.1
outcome
Check only, differential: the check fires on the vulnerable build and is silent on the patched one.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-11-18 15:23Zbleepingcomputer: trigger signal, started the run
- 2026-11-18 15:23Zcve.org record for CVE-2026-123633
- 2026-11-18 18:31Z10-Year-Old NGINX HTTP/2 Flaw Lets Unauthenticated Attackers Execute Code on Servers
- 2026-11-19 16:02ZLLCForge/CVE-2026-123633
this entry in the feed
GET /api/v1/feed/CVE-2026-123633
{ "etk_id": "ETK-2026-4940", "cve_id": "CVE-2026-123633", "display_id": "CVE-2026-123633", "ghsa_id": "GHSA-7xxj-p8w5-434q", "euvd_id": "EUVD-2026-128944", "status": "published", "anchor_state": "anchored", "title": "Use-after-free in NGINX HTTP/2 reverse proxy", "summary": "NGINX Open Source and NGINX Plus deployments acting as HTTP/2 reverse proxies are affected. A remote unauthenticated client may crash a worker process and, in environments without effective ASLR protection, may be able to execute code. Exposure depends on HTTP/2 being enabled for client connections, proxying to an upstream backend, and worker connections becoming scarce.", "mitigation": "Disable HTTP/2 on externally reachable NGINX listeners, such as by removing HTTP/2 listener configuration or setting `http2 off;`. Keep worker-connection capacity under review and obtain the vendor-supported patched package for the deployed distribution or NGINX release.", "vendor": "F5", "product": "NGINX Open Source", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 1.31.0, < 1.31.9", ">= 1.30.0, < 1.30.7", ">= 1.19.7, < *" ], "ecosystem": null, "fixed_versions": [ "1.31.9", "1.30.7", "*" ], "package_name": "NGINX Open Source", "purl": null }, { "affected_notes": [], "affected_ranges": [ ">= 37.1.0.1, < 37.2.0.1", ">= 37.0.0.1, < 37.0.7.1", ">= R33, < *" ], "ecosystem": null, "fixed_versions": [ "37.2.0.1", "37.0.7.1", "*" ], "package_name": "NGINX Plus", "purl": null } ], "cwes": null, "cvss_score": 8.1, "cvss_src": "other", "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H", "epss_score": null, "epss_percentile": null, "epss_asof": null, "automation": "deterministic", "check": true, "check_confidence_basis": "differential", "exploit": false, "pipeline_minutes": 25.074068716666666, "t0_at": "2026-11-18T15:23:27.197000+00:00", "signals": { "check": { "at": "2026-11-19T16:01:44.552513+00:00", "days": 1.0265897628819445, "is_lower_bound": false, "measured_at": "2026-11-18T15:23:27.197000+00:00", "url": null }, "public_poc": { "at": "2026-11-18T16:40:57+00:00", "days": 0.053817164351851854, "is_lower_bound": false, "measured_at": "2026-11-18T15:23:27.197000+00:00", "url": "https://github.com/LLCForge/CVE-2026-123633" }, "trigger_signal": { "at": "2026-11-18T15:23:27.197000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-11-18T15:23:27.197000+00:00", "url": "https://www.bleepingcomputer.com/news/security/critical-nginx-nginx2root-bugs-let-attackers-hijack-servers/" } } }
published 2026-11-19 15:36Z
last change 2026-11-19 19:03Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.