NGINX Security Update: How to Find, Mitigate and Patch CVE-2026-123007 and Related Vulnerabilities

NGINX Security Update: How to Find, Mitigate and Patch CVE-2026-123007 and Related Vulnerabilities

Multiple security vulnerabilities have been identified in NGINX, affecting components such as the resolver, HTTP/2, HTTP/3, and TLS 1.3 request processing.

The vulnerabilities include CVE-2026-123007, CVE-2026-123634, CVE-2026-121810, CVE-2026-123633, and CVE-2026-118899, with affected versions varying by vulnerability. Across these issues, vulnerable NGINX versions range from 0.6.18 through 1.31.8.

NGINX has released fixed versions for the affected branches:

  • Stable branch: Upgrade to 1.30.7 or a later 1.30.x release

  • Mainline branch: Upgrade to 1.31.9 or later


Vulnerability Details  

CVE ID

Vulnerability

Severity

Vulnerable Versions

Not Vulnerable

CVE-2026-123634

Use-after-free during response processing in resolver

Severe

0.6.18–1.31.8

1.31.9+, 1.30.7+

CVE-2026-123007

Memory corruption in HTTP/2 flow control

Critical

1.9.5–1.31.8

1.31.9+, 1.30.7+

CVE-2026-121810

Use-after-free in HTTP/3

Severe

1.25.0–1.31.8

1.31.9+, 1.30.7+

CVE-2026-123633

Use-after-free in HTTP/2

Severe

1.19.7–1.31.8

1.31.9+, 1.30.7+

CVE-2026-118899

Infinite loop while reading client request body over TLS 1.3

Critical

1.13.0–1.31.8

1.31.9+, 1.30.7+

 

Patch Details  

Linux Patch Details  

Bulletin ID

Patch IDs

Patch Description

ALAS2023-2026-3494

2837615, 2837616, 2837617, 2837618, 2837619, 2837620, 2837621, 2837622, 2837623, 2837624

nginx Security Update (ALAS2023-2026-3494)

ALAS2NGINX1-2026-018

2837625, 2837626, 2837627, 2837628, 2837629, 2837630, 2837631, 2837632, 2837633, 2837634, 2837635

nginx Security Update (ALAS2NGINX1-2026-018)

ALSA-2026:98527

3036367, 3036368, 3036369, 3036370, 3036372, 3036373, 3036374, 3036375, 3036376

Important: nginx:1.26 security update

ALSA-2026

3037609, 3037610, 3037611, 3037612, 3037613, 3037614, 3037615, 3037616, 3037617

Critical: nginx security update

 

Administrators can deploy the applicable NGINX security update either by searching for the relevant Patch ID or Bulletin ID in the Supported Patches view, or directly from the Threats → Vulnerabilities section by selecting the affected vulnerability and clicking on Install Patches.


Recommended Action  

 

  • Identify affected systems through the Vulnerabilities view. In Vulnerability Manager Plus, navigate to Threats → Vulnerabilities → Affected Systems.

  • For systems on the stable branch, upgrade to NGINX 1.30.7 or a later 1.30.x release.

  • For systems on the mainline branch, upgrade to NGINX 1.31.9 or later.

  • Prioritize internet-facing and business-critical NGINX servers.

  • Where NGINX is bundled within another product or appliance, obtain and apply the fixed version provided by the respective vendor.

  • After upgrading, verify that the running NGINX version is no longer within the affected range.


Embedded NGINX Bundles

The same NGINX vulnerabilities may also affect appliances that include an embedded NGINX bundle.


  1. If Drive Scan is not enabled in your environment, contact the relevant ManageEngine support team to enable it. Drive Scan can then be used to identify vulnerable NGINX binaries present within embedded NGINX bundles on managed endpoints.

  • In Vulnerability Manager Plus, navigate to Threats → Vulnerabilities and search for the relevant NGINX CVE.

  • In Endpoint Central, navigate to Threats & Patches → Threats → Vulnerabilities and search for the relevant NGINX CVE.

  • Click Affected Systems and refer to the Detected Path column to identify the embedded NGINX bundle associated with the vulnerability.

  • For vulnerabilities identified through Drive Scan, obtain the fixed version from the respective application or appliance vendor and update the affected embedded NGINX bundle.

  • After updating, run or wait for the next vulnerability scan and verify that the relevant vulnerability is no longer listed for the affected systems in the Vulnerabilities view


For embedded NGINX bundles, customers should use the vendor-provided fixed build rather than replacing the bundled NGINX component independently.


Temporary Mitigation: Disable HTTP/2  

If immediate patching is not possible, F5 recommends disabling HTTP/2 as a temporary mitigation for CVE-2026-123007 and CVE-2026-123633. This does not address the other listed vulnerabilities, and upgrading to a fixed version remains the permanent fix.

 

For more information, refer to the official NGINX security advisories:

https://nginx.org/en/security_advisories.html

Regards,
The ManageEngine Team