Quick answers
- Is CVE-2026-123633 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-123633 being exploited in the wild.
- How severe is CVE-2026-123633?
- High severity, with a CVSS score of 8.1, published 18 November 2026.
- Which products and versions are affected?
- NGINX NGINX Plus; NGINX NGINX Open Source.
- Is there a fix for CVE-2026-123633?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-123633 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-123633?
- Check whether you run Google Cloud Platform, NGINX Open Source or NGINX Plus. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A use-after-free vulnerability exists in NGINX Plus and NGINX Open Source when HTTP/2 is enabled for client connections and the worker process is under memory pressure (low worker_connections). An attacker can send a specially crafted request to trigger the vulnerability, achieving denial-of-service or remote code execution on systems without ASLR or where ASLR can be bypassed. The issue is data-plane only with no control plane exposure.
Affected products
- NGINX NGINX Plus
- NGINX NGINX Open Source
Identifiers
- CVE-2026-123633
- CVE-2026-123007
Timeline
- 2026-11-18: disclosed