← All security briefings

Attention

nginx 1.31.9 and 1.30.7 fix five memory corruption flaws in HTTP/2, HTTP/3, resolver and mail proxy paths

Identifiers: CVE-2026-123007 · CVE-2026-123633 · CVE-2026-123634 · CVE-2026-121810 · CVE-2026-113425

Published
Last substantive change
Last verified

Last verified: . Attention items are due for re-verification within 72 hours.

Summary

On 18 November 2026 the nginx project released 1.31.9 and stable 1.30.7, fixing five separate memory corruption issues (CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, CVE-2026-121810, CVE-2026-113425). Researchers call the set nginx2root; that is a research label, not a finding that the flaws grant root. Each issue needs its own feature path to be enabled and reachable.

Classification reason: Attention: CVE-2026-123007 reaches any HTTP/2 listener on an unpatched build and allows unauthenticated worker crashes; code execution depends on an ASLR condition and no in-the-wild exploitation is established in the reviewed sources.

Impact

A remote unauthenticated attacker reaching an affected feature can crash an nginx worker, causing denial of service. Per F5, code execution also needs ASLR disabled or bypassed and runs with the worker's permissions, not automatically root; ASLR or PIE being on does not prove safety. CVE-2026-123007 needs only an HTTP/2 listener on an unpatched build. CVE-2026-123633 also needs proxied requests and a worker low on worker_connections. CVE-2026-123634 needs a variable proxied server name plus an SSI or mirror subrequest resolving it. CVE-2026-121810 needs HTTP/3 plus further conditions. CVE-2026-113425 needs the mail proxy. One matching path is enough.

Who is affected

Official nginx index ranges: CVE-2026-123007 1.9.5–1.31.8; CVE-2026-123633 1.19.7–1.31.8; CVE-2026-123634 0.6.18–1.31.8; CVE-2026-121810 1.25.0–1.31.8; CVE-2026-113425 0.5.33–1.31.8. Fixed in 1.31.9 or stable 1.30.7. Distribution and vendor builds may backport fixes under older version numbers, so a version banner alone is not proof. NGINX Plus is packaged separately and is not covered here.

Products and versions

Products and versionsAffectedFixed
NGINX Open Source (CVE-2026-123007) 1.9.5–1.31.8 1.31.9 or stable 1.30.7; distribution/vendor backports require their own confirmation
NGINX Open Source (CVE-2026-123633) 1.19.7–1.31.8 1.31.9 or stable 1.30.7; distribution/vendor backports require their own confirmation
NGINX Open Source (CVE-2026-123634) 0.6.18–1.31.8 1.31.9 or stable 1.30.7; distribution/vendor backports require their own confirmation
NGINX Open Source (CVE-2026-121810) 1.25.0–1.31.8 1.31.9 or stable 1.30.7; distribution/vendor backports require their own confirmation
NGINX Open Source (CVE-2026-113425) 0.5.33–1.31.8 1.31.9 or stable 1.30.7; distribution/vendor backports require their own confirmation

Exploitation evidence

Exploitation not established. As of 19 November 2026 the nginx advisory index and the reviewed F5 CNA records report no exploitation in the wild, and the CISA Known Exploited Vulnerabilities catalogue dated 18 November did not list these five IDs. Researchers have reported laboratory proofs. Absence from these sources is not proof that no attacks are occurring.

Sources: nginx project

Actions

  1. Inventory every nginx you run: website host, control panel, containers, Kubernetes ingress, appliances.
  2. Confirm which features your origin servers actually enable: HTTP/2, HTTP/3, SSI or mirror with variable proxied names, mail proxy, not just the CDN in front.
  3. Update to 1.31.9, stable 1.30.7 or your vendor's confirmed backport after a compatibility test, with a rollback path.
  4. Rebuild and redeploy container images; a host package update does not patch nginx inside containers.
  5. Fully restart nginx or perform the documented live binary upgrade and drain old workers; a configuration reload keeps the old binary running.
  6. Ask your provider to confirm the running binary and listener settings, then watch error rates and key customer journeys.

Unknowns

  • Whether a specific site has the required features enabled, or has already been targeted, is unknown without checking.
  • The additional conditions required for CVE-2026-121810 are not fully described in the public sources.
  • Backport status for individual distributions and hosting panels is unconfirmed here.

Sources

  • nginx project · retrieved https://nginx.org/en/security_advisories.html
  • nginx project · retrieved https://nginx.org/en/CHANGES
  • F5 / CVE CNA · published · updated · retrieved https://cveawg.mitre.org/api/cve/CVE-2026-123007
  • F5 / CVE CNA · published · updated · retrieved https://cveawg.mitre.org/api/cve/CVE-2026-123633
  • F5 / CVE CNA · published · updated · retrieved https://cveawg.mitre.org/api/cve/CVE-2026-123634
  • F5 / CVE CNA · published · updated · retrieved https://cveawg.mitre.org/api/cve/CVE-2026-121810
  • F5 / CVE CNA · published · updated · retrieved https://cveawg.mitre.org/api/cve/CVE-2026-113425
  • nginx project · retrieved https://nginx.org/en/docs/control.html
  • Wiz Research · retrieved https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities
  • CISA · retrieved https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json

Change history

  1. — Published: 19 November 2026: Published briefing on five nginx memory corruption issues (CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, CVE-2026-121810, CVE-2026-113425) fixed in 1.31.9 and stable 1.30.7, released 18 November 2026. Exploitation not established in reviewed sources; priority attention.

Subscribe: RSS feed · JSON Feed · Feed format and fields