> ## Content Index
> Fetch the complete content index at: https://ping2prompt.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# nginx 1.30.7 and 1.31.9 fix ten vulnerabilities, upgrade now
- URL: https://ping2prompt.com/nginx-1307-and-1319-fix-ten-vulnerabilities-upgrade-now/
- Published: 2026-11-18T17:06:40.000Z
- Updated: 2026-11-18T19:05:43.000Z
- Description: nginx released stable 1.30.7 and mainline 1.31.9 on 2026-11-18, fixing ten CVEs across the resolver, HTTP/2, HTTP/3, mail proxy and stream modules. Exploitation status is unknown. Upgrade stable installs to 1.30.7 and mainline installs to 1.31.9.
- Author: Ping2Prompt Newsroom
- Tags: NGINX, Self-hosted, Patches, Critical, #updated, #short-ping

**Update (2026-11-18):** Exploitation status: unknown: primary sources do not report in-the-wild exploitation. Cyberscoop reports researchers say five disclosed NGINX flaws each have a working exploit., according to [cyberscoop.com/nginx-critical-vulnerabilities-exploits](https://cyberscoop.com/nginx-critical-vulnerabilities-exploits/?ref=ping2prompt.com).

## nginx 1.30.7 and 1.31.9 fix ten vulnerabilities

nginx released stable 1.30.7 and mainline 1.31.9 on 2026-11-18, and both carry vulnerability fixes. The fixes cover ten CVEs in the resolver, HTTP/2, HTTP/3, TLS 1.3 body reading, mail proxy, PROXY protocol, alias with try\_files, and the stream module.

The exploitation status is unknown: the announcement does not say whether any of these flaws are being attacked. It follows a 2026-10-14 release that fixed five other CVEs.

## The announcement lists no affected version ranges

nginx names only the fixed releases: 1.30.7 on the stable branch and 1.31.9 on the mainline branch. It does not state which earlier versions are vulnerable, so treat any build older than these two as exposed. To judge your own exposure, compare your running version with the fixed ones and check whether your configuration uses the affected components listed below.

## Flaws span resolver, HTTP/2, HTTP/3 and stream modules

The announcement gives one line per CVE and no per-CVE severity. These eight are the main ones:

- **CVE-2026-123634**: use-after-free in the resolver.
- **CVE-2026-123007**: memory corruption in HTTP/2 flow control.
- **CVE-2026-121810**: use-after-free in HTTP/3.
- **CVE-2026-123633**: use-after-free in HTTP/2.
- **CVE-2026-118899**: infinite loop while reading a client request body over TLS 1.3.
- **CVE-2026-113425**: use-after-free in the mail proxy module.
- **CVE-2026-125283**: buffer overflow when using alias with try\_files.
- **CVE-2026-120967**: SNI bypass in client certificate validation in the stream module. The other two are CVE-2026-120993, a NULL pointer dereference with PROXY protocol version 2, and CVE-2026-123640, insufficient validation in the stream ssl\_preread module.

## Update to nginx 1.30.7 or 1.31.9

Upgrade stable installs to 1.30.7 and mainline installs to 1.31.9\. The announcement gives no CVSS scores, no workarounds and no word on exploitation, so the update is the only step it offers. Watch nginx.org for any follow-up with severity details or mitigations.

| Product        | Affected                       | Fixed  |
| -------------- | ------------------------------ | ------ |
| nginx stable   | Not stated in the announcement | 1.30.7 |
| nginx mainline | Not stated in the announcement | 1.31.9 |

## Sources

- [cyberscoop.com/nginx-critical-vulnerabilities-exploits](https://cyberscoop.com/nginx-critical-vulnerabilities-exploits/?ref=ping2prompt.com)
- [nginx.org](http://nginx.org/?ref=ping2prompt.com#2026-11-18)

---

This story was produced with AI assistance from the sources listed above and fact-checked against them before publication. Read our [editorial methodology](https://ping2prompt.com/about-how-we-work/) and the [corrections log](https://ping2prompt.com/corrections/). Spotted an error? Email [editor@ping2prompt.com](mailto:editor@ping2prompt.com).