Microsoft maps Azure Linux NGINX fixes; check feature paths

An NGINX package version does not tell you which request paths need attention. For this Azure Linux update, HTTP/2, mail proxying, stream routing and client-certificate settings decide the applicability checks.

Teal network paths pass through a transparent gateway toward three unbranded server racks.

What is new

MSRC published eight Azure Linux 3.0 NGINX mappings on November 20, 2026, at 01:01:44–01:02:27 UTC (November 19, 8:01–8:02 p.m. Eastern). Each names 1.30.6-2 as the fixed distribution build. This review verifies the exact nginx-1.30.6-2.azl3 package in Microsoft’s x86-64 and ARM64 production metadata. The downloaded x86-64 RPM matches the repository SHA-256 checksum.

This is a newly verified Microsoft product-remediation cluster, following the earlier pending review. Repository availability does not mean the package was installed on a customer host or included in every container or AKS image. No customer deployment is assumed.

Affected paths and vendor scores

CVEMSRC severity / CVSS 3.1Configuration or input pathUpstream introduced version
CVE-2026-113425Critical / 8.1Mail proxy; memory corruption and possible RCE.0.5.33
CVE-2026-123007Critical / 8.1HTTP/2 flow-control processing; heap corruption and possible RCE.1.9.5
CVE-2026-123633Critical / 8.1HTTP/2 client requests proxied to a backend while worker_connections is low; use-after-free.1.19.7
CVE-2026-123634Critical / 8.1Proxy hostname variables plus SSI or mirror subrequests resolving that same name; resolver use-after-free.0.6.18
CVE-2026-118899Important / 7.5HTTP listen with ssl and TLS 1.3; crafted request-body traffic can leave a worker looping.1.13.0
CVE-2026-120967Moderate / 4.8ssl_verify_client on in a non-default stream virtual server; client-certificate verification bypass.1.25.5
CVE-2026-123640Moderate / 5.3ngx_stream_ssl_preread_module; forged ClientHello-derived variables can defeat intended stream routing.1.15.2
CVE-2026-125283Moderate / 5.3try_files plus alias with a map variable and particular regex captures; worker crash.0.9.6

The first four issues can corrupt worker memory. F5 describes possible remote code execution when ASLR is disabled or can be bypassed; a worker crash alone is not proof of code execution. F5 characterizes these as data-plane issues, rather than NGINX control-plane exposure. Validate the actual running modules, configuration and reachable input path.

Score attribution: the table uses MSRC’s severity and CVSS 3.1 values. F5’s CNA records give the same numeric CVSS 3.1 scores, but label the first four High and publish CVSS 4.0 scores of 9.2. F5’s CVSS 4.0 scores for CVE-2026-118899, CVE-2026-120967, CVE-2026-123640 and CVE-2026-125283 are 8.7, 6.3, 6.9 and 6.9 respectively. These vendor labels and scoring versions are distinct.

Fixed versions and limits

Azure Linux 3.0: MSRC explicitly names fixed build 1.30.6-2, and Microsoft distributes it as 1.30.6-2.azl3. Its affected-product row is the placeholder nginx 0.0.0-1, so it does not establish a precise affected distribution range. Do not treat that placeholder as an installed version or invent a universal older-build bound. Confirm the installed package release and supported upgrade path with the distribution.

Upstream NGINX Open Source: the official security index identifies fixed branches 1.30.7+ and 1.31.9+ for all eight. In the current stable and mainline branches, 1.30.0–1.30.6 and 1.31.0–1.31.8 are affected when the relevant feature path applies. The index also lists older versions starting at the introduced versions in the table. Its broad ranges ending at 1.31.8 must be read together with the fixed 1.30.7+ exception. These upstream bounds are not Azure Linux package bounds, and this article does not supply an NGINX Plus upgrade matrix.

The public Microsoft 3.0 source-branch spec still shows 1.30.6 release 1 at verification. The production release-2 RPM is separate evidence; its changelog says upstream fixes were applied while retaining 1.30.6, without enumerating these eight CVEs. The distribution fix attribution comes from MSRC’s per-CVE fixed-build fields. Functional validation or a complete backport-code audit was not performed; use Microsoft’s supported package and resolve any deployment-specific uncertainty before closing remediation.

Exploitation and MSP action

All eight CVEs are absent from the full CISA KEV catalog checked November 20. Confirmed malicious exploitation was not verified in the reviewed official material; there is no KEV federal due date for these CVEs. Potential exploit impact and published vulnerability details are not confirmed attacks. No blanket credential-rotation or incident-response requirement was identified.

Suggested MSP priority: High for applicable internet-facing or trust-boundary paths. Inventory the actual OS, package release, loaded NGINX process, modules, configuration and external reachability. Prioritize HTTP/2 and mail/resolver memory-corruption paths, and stream configurations enforcing client identity or backend segmentation.

If needed while validating the fix, restrict unnecessary reachability or retire an unused affected feature through tested change control. That is proposed exposure reduction, not a verified vendor workaround. Roll out the supported signed distribution package through a pilot, then verify the running package release and all restarted or replaced workers. Test HTTP/2, proxying, TLS 1.3, client-certificate rejection, intended stream routing and legitimate application traffic as applicable. Rebuild or update separate bundled/container deployments through their supported paths; a host update does not repair every image.

Official sources

MSRC November CVRF and publication records · NGINX security index · Microsoft x86-64 repository metadata · Microsoft ARM64 repository metadata · Microsoft source-branch spec · Microsoft upgrade guidance · CISA full KEV data.

F5-authored CNA records: CVE-2026-113425 · CVE-2026-123007 · CVE-2026-123633 · CVE-2026-123634 · CVE-2026-118899 · CVE-2026-120967 · CVE-2026-123640 · CVE-2026-125283. Last verified November 20, 2026 UTC. F5’s linked support article rendered a shell in the prior review; the accessible vendor-authored records supply the feature prerequisites above.

Share this article