NGINX 1.31.9 and 1.30.7 Fix Protocol and Configuration Vulnerabilities

P2 — VALIDATE AND UPDATENot provided by the authority · Not provided by the authorityEXPLOITATION: NOT STATED

Quick Answer

Upgrade affected nginx deployments to the matching fixed branch and validate HTTP/2, HTTP/3, TLS client authentication, routing and mail proxy behavior.

Confirm Scope And Apply The Supported Remediation

What to do now: Record nginx distribution and version, build modules, enabled protocols, resolver use, alias/try_files rules, stream listeners and mail proxy roles. Use the per-CVE ranges and feature prerequisites. A listed broad range does not override the explicit fixed stable release. Distribution backports and NGINX Plus require their own supplier confirmation. Deploy the supported nginx 1.31.9 or 1.30.7 release for the installed branch, or the corresponding distribution-supported fix. Validate configuration and complete a controlled service transition so active workers use the corrected code. Verify active binaries and worker turnover. Test upstream routing, file mappings, DNS, client certificates and required protocols; retain configuration diffs, build provenance, service tests and rollback evidence.

Open the authoritative advisory

Last verified: 2026-11-18 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeOpen-source nginx HTTP, stream and mail modules
Advisorynginx-1.31.9-1.30.7-security-release
CVEsCVE-2026-113425, CVE-2026-118899, CVE-2026-120967, CVE-2026-120993, CVE-2026-121810, CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, CVE-2026-123640, CVE-2026-125283
Authoritative release date2026-11-18 — project release date. The project’s annotated release-1.31.9 tag was created at 15:24:22 UTC, corroborating release activity after the monitoring cutoff; the advisory date itself has day precision.
Authority revision dateNo separate material revision is established for this release.
Affected versionsAffected version ranges and prerequisite features differ by CVE; see the project matrix below. The PROXY v2 issue is limited to 1.31.4–1.31.8. The other nine fixes are included in both release branches.
Fixed versionnginx 1.31.9 on mainline or 1.30.7 on stable, as applicable; CVE-2026-120993 is a mainline-only issue fixed in 1.31.9.
CVSS base scoreNot provided by the authority
CVSS severityNot provided by the authority
Exploitation statusThe cited authority does not confirm exploitation of these vulnerabilities in the wild.; no exploitation claim is inferred.

What Changed

The project released ten mainline security fixes and nine stable-branch fixes covering HTTP/2, HTTP/3, DNS resolution, TLS, stream processing, file-path mapping and mail proxying. Its advisory uses major, medium and minor impact labels without publishing CVSS base scores.

What To Validate Now

  1. Inventory. Record nginx distribution and version, build modules, enabled protocols, resolver use, alias/try_files rules, stream listeners and mail proxy roles.
  2. Establish applicability. Use the per-CVE ranges and feature prerequisites. A listed broad range does not override the explicit fixed stable release. Distribution backports and NGINX Plus require their own supplier confirmation.
  3. Remediate. Deploy the supported nginx 1.31.9 or 1.30.7 release for the installed branch, or the corresponding distribution-supported fix. Validate configuration and complete a controlled service transition so active workers use the corrected code.
  4. Validate. Verify active binaries and worker turnover. Test upstream routing, file mappings, DNS, client certificates and required protocols; retain configuration diffs, build provenance, service tests and rollback evidence.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

These are distinct configuration-dependent flaws. Do not infer code execution or active exploitation for every CVE. This release also rejects malformed header lines and excessive chunk framing, so test dependent applications for compatibility.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Release-Specific Version Matrix

CVERelevant featureAffected project versionsFixed project versions
CVE-2026-123634Resolver response processing0.6.18–1.31.81.31.9+ or 1.30.7+
CVE-2026-123007HTTP/2 flow control1.9.5–1.31.81.31.9+ or 1.30.7+
CVE-2026-121810HTTP/3 with insufficient worker connections1.25.0–1.31.81.31.9+ or 1.30.7+
CVE-2026-123633HTTP/2 with insufficient worker connections1.19.7–1.31.81.31.9+ or 1.30.7+
CVE-2026-118899TLS 1.3 request-body processing1.13.0–1.31.81.31.9+ or 1.30.7+
CVE-2026-113425Mail proxy0.5.33–1.31.81.31.9+ or 1.30.7+
CVE-2026-120993PROXY v2 with dynamic TLS certificates1.31.4–1.31.81.31.9+
CVE-2026-125283Combined alias and try_files configuration0.9.6–1.31.81.31.9+ or 1.30.7+
CVE-2026-120967Stream TLS client-certificate verification and SNI1.25.5–1.31.81.31.9+ or 1.30.7+
CVE-2026-123640Stream TLS preread1.15.2–1.31.81.31.9+ or 1.30.7+

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.