Security

CVE-2026-123007: nginx HTTP/2 Memory Corruption - Is Your Server Affected?

Back to Blog
A modern alternative to cPanel, Plesk and CyberPanel — isolated, secure, AI-assisted.
Start free

Short answer: nginx published ten advisories on 18 November 2026. They are fixed in 1.31.9 (mainline) and 1.30.7 (stable). Three carry the "major" rating, and two of those three reach a normal web server: CVE-2026-123007 (memory corruption in HTTP/2 flow control) and CVE-2026-118899 (infinite loop while reading a request body over TLS 1.3). Panelica published nginx 1.31.9 for both its customer and panel web servers.

The three major ones

  • CVE-2026-123007 - memory corruption in HTTP/2 flow control. Relevant to anyone serving HTTP/2, which today is almost everyone.
  • CVE-2026-118899 - infinite loop while reading a client request body over TLS 1.3. The only precondition is TLS 1.3.
  • CVE-2026-113425 - use-after-free in the mail proxy module. Only applies if that module is compiled into your binary; nginx -V shows whether it is.

The other seven, and why several will not apply to you

The remaining advisories are CVE-2026-121810 (HTTP/3), CVE-2026-123634 (use-after-free in the resolver), CVE-2026-123633 (use-after-free in HTTP/2), CVE-2026-120967 and CVE-2026-123640 (the stream module), CVE-2026-120993 (PROXY protocol version 2) and CVE-2026-125283 (buffer overflow when alias is used with try_files).

Several of those depend on a module being compiled in or a directive being used. That is worth checking before treating the batch as ten problems: an advisory for a module your binary does not contain is not an exposure. In our own build, for example, HTTP/3, the mail proxy and the stream module are not compiled in, the PROXY protocol is not used anywhere in the configuration we generate, and the vhosts we generate for customer domains contain no alias directive at all - so four of the ten reach our customer web server and six do not.

The earlier batch that 1.31.6 is still missing

This is the part that is easy to overlook. If you are on 1.31.6, you are not only missing the 18 November batch; you are also missing the one that closed in 1.31.7. Two from that batch are worth naming:

  • CVE-2026-15176 - buffer overflow when alias and rewrite appear in the same location block.
  • CVE-2026-97629 - session forgery through TLS session tickets. Note that ssl_session_tickets is on by default in nginx, so the absence of that directive in your configuration means it is enabled, not disabled.

About disabling HTTP/2 as a stop-gap

Turning HTTP/2 off is a reasonable temporary step, but be clear about what it buys: it covers the issues that need HTTP/2, and nothing else. CVE-2026-118899 needs only TLS 1.3, and the resolver issue has nothing to do with HTTP/2. Upgrading is the actual fix.

What Panelica did

We build nginx from the signed upstream source ourselves, so we assess each advisory against our own build and configuration instead of forwarding the vendor's list. For this batch we published nginx 1.31.9 for customer sites and nginx-panel 1.31.9 for the panel's own web server. Both were built with the same configure arguments and library dependencies as the previous release, both passed the functional matrix on all nine supported operating systems, both matched the previous package's file set exactly, and both were applied through the panel's own update path on a server installed from the published release, including a reboot afterwards.

Existing servers pick them up under Updates in the panel, or with panelica package apply.

Security-first hosting panel

Hosting management, the modern way.

Panelica is a modern, security-first hosting panel — isolated services, built-in Docker and AI-assisted management, with one-click migration from any panel.

Zero-downtime migration Fully isolated services Cancel anytime
Share:
When did you last test a restore?