# NGINX fixes HTTP/2 flaw present since 2015 that could let attackers run code remotely

> NGINX released 1.31.9 and 1.30.7 on Nov. 18, 2026, fixing CVE-2026-123007, an HTTP/2 flaw that could let attackers run code remotely.

*nginx.org lists versions 1.9.5 to 1.31.8 as vulnerable, and the fixed releases are 1.31.9 mainline and 1.30.7 stable.*

- Type: News
- Section: Tech
- By: Tech Desk
- Published: 2026-11-18T17:40:00-05:00
- Updated: 2026-11-18T17:40:00-05:00
- Checked: 2026-11-18T17:39:03-05:00
- URL: https://factsdesk.com/tech/nginx-vulnerability/

## Key facts

- NGINX released 1.31.9 mainline and 1.30.7 stable on Nov. 18, 2026, fixing CVE-2026-123007, a memory corruption flaw in HTTP/2 flow control. Source: [nginx.org](https://nginx.org/). Confirmed 2026-11-18T17:39:03-05:00. Cite: https://factsdesk.com/tech/nginx-vulnerability/#nginx-released-1-31-9-mainline-and-1-30-7-stable-on-nov-18
- The CVE record says attackers can execute code on systems with ASLR disabled or when they can bypass ASLR, and that the flaw can also crash the NGINX worker process or corrupt its memory. Source: [CVE Program](https://www.cve.org/CVERecord?id=CVE-2026-123007). Confirmed 2026-11-18T17:39:03-05:00. Cite: https://factsdesk.com/tech/nginx-vulnerability/#the-cve-record-says-attackers-can-execute-code-on-systems
- nginx.org rates the flaw major and lists NGINX 1.9.5 to 1.31.8 as vulnerable, with 1.31.9 and later and 1.30.7 and later not vulnerable. Source: [nginx.org](https://nginx.org/en/security_advisories.html). Confirmed 2026-11-18T17:39:03-05:00. Cite: https://factsdesk.com/tech/nginx-vulnerability/#nginx-org-rates-the-flaw-major-and-lists-nginx-1-9-5-to-1-31
- The CVE record gives the flaw a CVSS 3.1 base score of 8.1 (High) and a CVSS 4.0 base score of 9.2 (Critical), with no privileges and no user interaction required. Source: [CVE Program](https://www.cve.org/CVERecord?id=CVE-2026-123007). Confirmed 2026-11-18T17:39:03-05:00. Cite: https://factsdesk.com/tech/nginx-vulnerability/#the-cve-record-gives-the-flaw-a-cvss-3-1-base-score-of-8-1
- The HTTP/2 module that holds the flaw first shipped in NGINX 1.9.5 on Sep. 22, 2015. Source: [nginx.org](https://nginx.org/en/CHANGES). Confirmed 2026-11-18T17:39:03-05:00. Cite: https://factsdesk.com/tech/nginx-vulnerability/#the-http-2-module-that-holds-the-flaw-first-shipped-in-nginx

## What is known

Verified:
- NGINX released the fixed versions 1.31.9 and 1.30.7 on Nov. 18, 2026, and the CVE record lists no workaround.
- A CISA assessment added to the CVE record at 16:04 UTC on Nov. 18, 2026, recorded exploitation as none.

Not yet known:
- The traffic that triggers the flaw. The CVE record describes it only as undisclosed traffic.

On Nov. 18, 2026, NGINX [released 1.31.9 mainline and 1.30.7 stable](https://nginx.org/) with fixes for 10 security flaws, among them CVE-2026-123007, a memory corruption flaw in HTTP/2 flow control that the CVE record says could let attackers execute code.

## What happened

The [nginx.org news entry](https://nginx.org/) for Nov. 18, 2026, lists "memory corruption in HTTP/2 flow control (CVE-2026-123007)" among the vulnerability fixes in the two releases. The [nginx changelog](https://nginx.org/en/CHANGES) for 1.31.9 says a flow control window overflow in HTTP/2 might allow an attacker to cause a segmentation fault in a worker process, or might have other potential impact.

The [CVE record](https://www.cve.org/CVERecord?id=CVE-2026-123007), filed by F5 and published on Nov. 18, 2026, says the issue affects NGINX Plus and NGINX Open Source configurations that use HTTP/2. When NGINX processes undisclosed traffic, the record says, the flow control window can exceed the allowed threshold, which can lead to a heap buffer overflow that is typically followed by a crash of the worker process. The same record says attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR. It describes the flaw as a data plane issue only, with no control plane exposure.

The record's CVSS vectors set privileges required and user interaction to none, and the attack vector to network. They also set attack complexity to high.

## The numbers

These figures are from the [nginx.org security advisories page](https://nginx.org/en/security_advisories.html) and the [CVE record](https://www.cve.org/CVERecord?id=CVE-2026-123007):

| Item | What the record says | Source |
| --- | --- | --- |
| CVE id | CVE-2026-123007 | nginx.org and CVE record |
| Severity | Major | nginx.org |
| Vulnerable versions | 1.9.5 to 1.31.8 | nginx.org |
| Fixed versions | 1.31.9 and later, 1.30.7 and later | nginx.org |
| CVSS 3.1 base score | 8.1 (High) | CVE record |
| CVSS 4.0 base score | 9.2 (Critical) | CVE record |
| Weakness types | CWE-191 integer underflow, CWE-787 out-of-bounds write | CVE record |

For NGINX Plus, the [CVE record](https://www.cve.org/CVERecord?id=CVE-2026-123007) lists versions from 37.0.0 up to but not including 37.0.8.1, and from 37.1.0 up to but not including 37.3.0.1, as affected, along with releases from R33.

## What the record says comes next

The fix is in NGINX 1.31.9 mainline and 1.30.7 stable, both [released on Nov. 18, 2026](https://nginx.org/). The [CVE record](https://www.cve.org/CVERecord?id=CVE-2026-123007) lists the workaround as "None" and notes that software versions that have reached End of Technical Support are not evaluated. It links F5's advisory, K000163926, as the vendor advisory and patch.

A CISA assessment added to the [CVE record](https://www.cve.org/CVERecord?id=CVE-2026-123007) at 16:04 UTC on Nov. 18, 2026, recorded exploitation as none, automatable as no and technical impact as total.

## Background

The HTTP/2 module, ngx_http_v2_module, first shipped in [NGINX 1.9.5 on Sep. 22, 2015](https://nginx.org/en/CHANGES), replacing the SPDY module. For the port HTTPS uses by default, see [what port HTTPS uses](/tech/what-port-does-https-use/).

The same Nov. 18 releases fixed nine other flaws, according to the [nginx.org news entry](https://nginx.org/), including a use-after-free in HTTP/2 (CVE-2026-123633), which [nginx.org](https://nginx.org/en/security_advisories.html) rates medium and lists as affecting 1.19.7 to 1.31.8. The [CVE record](https://www.cve.org/CVERecord?id=CVE-2026-123007) credits Stephen Fewer of Rapid7, Tomer Schwartz of Wiz Research, Xint.io and Ikotas Labs with reporting CVE-2026-123007.

NGINX is an HTTP web server, reverse proxy, content cache, load balancer, TCP/UDP proxy server and mail proxy server, according to [nginx.org](https://nginx.org/). For the gateway status code a server can return, see [what HTTP 502 means](/tech/what-does-the-http-502-status-code-mean/).

## Sources

1. [nginx security advisories](https://nginx.org/en/security_advisories.html), nginx.org, 2026-11-18 (primary source)
2. [nginx news: nginx-1.30.7 stable and nginx-1.31.9 mainline released](https://nginx.org/), nginx.org, 2026-11-18 (primary source)
3. [CVE-2026-123007: NGINX ngx_http_v2_module vulnerability](https://www.cve.org/CVERecord?id=CVE-2026-123007), CVE Program, 2026-11-18 (primary source)
4. [Changes with nginx](https://nginx.org/en/CHANGES), nginx.org, 2026-11-18 (primary source)

## Asked next

- [What is a zero-day attack?](https://factsdesk.com/tech/what-is-a-zero-day-attack/): A zero-day attack exploits a previously unknown hardware, firmware, or software vulnerability, according to the NIST glossary definition.
- [What is a denial of service attack?](https://factsdesk.com/tech/what-is-a-denial-of-service-attack/): NIST defines denial of service as preventing authorized access to resources or delaying time-critical operations.
- [What is malware?](https://factsdesk.com/tech/what-is-malware/): Malware is hardware, firmware, or software intentionally included or inserted in a system for a harmful purpose, per NIST. The FTC lists next steps.
- [What port does HTTPS use?](https://factsdesk.com/tech/what-port-does-https-use/): HTTPS uses TCP port 443 by default: under RFC 9110, an https address with no port named goes to port 443, the reserved port for HTTP over TLS.
- [What port does HTTP use?](https://factsdesk.com/tech/what-port-does-http-use/): HTTP uses TCP port 80 by default. RFC 9110 makes port 80 the default for http URLs, and IANA assigns port 80 to the http service.
- [What does the HTTP 502 status code mean?](https://factsdesk.com/tech/what-does-the-http-502-status-code-mean/): HTTP 502 Bad Gateway means a server acting as a gateway or proxy received an invalid response from an inbound server, under RFC 9110.
