Linux Security · Debian 13 · nginx · 19.11.2026

November 2026 nginx vulnerabilities: check and mitigate on Debian 13

Ten nginx CVEs, a real Debian 13 server and original terminal evidence: from the temporary morning TLS workaround to the installed Debian security update and verified TLS 1.3 restoration that evening.

In this article
  1. Summary
  2. Evening update: deb13u11
  3. TLS 1.3 restored and tested
  4. Ten CVEs
  5. Debian packages
  6. Copy-and-paste checks
  7. Mitigation
  8. PHP releases
  9. FAQ
  10. Conclusion
  11. Sources

Quick summary: what you need to know

On 18 November 2026, nginx released 1.30.7 (stable) and 1.31.9 (mainline), addressing ten security issues. HTTP/2 memory corruption is particularly serious, while other flaws require HTTP/3, TLS 1.3, mail proxy, DNS resolver or stream-specific configurations. Whether a system is exploitable depends on its distribution patch level and enabled features.

All terminal images in this article are real captures from my Debian 13 server on 19 November 2026. The early captures were cropped and given headings; the new evening captures were only compressed to WebP. Visible responses are unaltered. Private admin routes and internal backend addresses are excluded.

Evening update, 19 November 2026 (CET): The corrected Debian 13 package 1.26.3-3+deb13u11 is available and installed on Worldnode. Debian identifies the fix in DSA-6642-1. nginx is running after the upgrade. TLS 1.3 was subsequently re-enabled after configuration validation and a reload. Protocol-specific local requests returned HTTP 200 over both TLS 1.2 and TLS 1.3 on both tested services. Session tickets remain disabled. The morning evidence below records the state before this update.

I documented a real Debian 13 production-host check on Worldnode: package version, nginx configuration, PHP detection, HTTP/2 and HTTP/3, TLS 1.3 and TLS 1.2. These are reproducible checks – not a penetration test or a claim of complete security.

Evening update: deb13u11 installed, nginx running

In the evening I refreshed the package lists again with sudo apt update. APT now offered nginx and nginx-common version 1.26.3-3+deb13u11 from trixie-security. After a successful sudo nginx -t, I ran sudo apt upgrade. Both nginx packages moved from deb13u10 to deb13u11. The same transaction updated tzdata from 2026c-0+deb13u1 to 2026f-0+deb13u1: three packages upgraded, none newly installed, removed or left unupgraded.

APT installs nginx and nginx-common deb13u11 plus tzdata 2026f.
The manual evening upgrade: both nginx packages configured successfully.

The subsequent systemctl status nginx --no-pager output reports active (running) since . Both the pre-start configuration test and startup exited with status=0/SUCCESS. This establishes package installation and the subsequent service start. These screenshots do not include a fresh HTTPS connection test after this upgrade.

nginx active since 18:40:14 CET, with successful configuration check and startup.
Post-upgrade check: nginx.service is enabled and running.

Immediately after the upgrade: TLS 1.3 still disabled

A configuration query immediately after the package update still showed two ssl_protocols TLSv1.2; directives and ssl_session_tickets off;. At that stage I had not yet re-enabled TLS 1.3. This was an interim operational decision for Worldnode: Debian now lists the November fixes, including CVE-2026-118899, under deb13u11. The earlier statement that the patch was pending describes the morning only. TLS 1.3 was restored in the separate, tested step documented below; disabling session tickets is a distinct setting.

Post-update configuration output: TLSv1.2 and ssl_session_tickets off.
Historical state immediately after the package upgrade, before TLS 1.3 was restored. New screenshots are only compressed to WebP; original PNG captures are retained.

Later that evening: TLS 1.3 restored and tested

After confirming that Debian marks CVE-2026-118899 as fixed in the installed 1.26.3-3+deb13u11 package, I removed the temporary TLS-1.3 restriction on 19 November 2026. Both configuration files were backed up before changing their protocol directives to ssl_protocols TLSv1.2 TLSv1.3;. The configuration passed sudo nginx -t, then I applied it with sudo systemctl reload nginx. The session-ticket setting was left unchanged.

I then ran protocol-specific HTTPS requests on Worldnode. Each request pinned both the minimum and maximum TLS version and used --resolve to connect directly to 127.0.0.1 with the public hostname for SNI and certificate verification. --noproxy '*' excluded a configured client proxy. All four requests returned HTTP 200:

ServiceTLS 1.2 onlyTLS 1.3 only
WebsiteHTTP 200HTTP 200
Social serviceHTTP 200HTTP 200

These results confirm working local HTTPS connections with certificate verification over both protocol versions after the reload. The test results were confirmed during the follow-up; no additional terminal screenshot is included for this step. They do not constitute an exploit test or a test from an external client. The earlier screenshots showing TLS 1.2 only remain above as the historical record of the temporary mitigation.

November 2026 nginx vulnerabilities: which features matter?

Ten CVEs does not mean ten exploitable paths on every server. Some require HTTP/2, others HTTP/3 with upstream forwarding, mail authentication, TLS 1.3, or specific alias/variable combinations. The relevant question is not just whether nginx is installed but which exposed functionality actually exists.

CVEComponentRelevant precondition
CVE-2026-123007HTTP/2 flow controlHTTP/2 flow control memory corruption
CVE-2026-123633HTTP/2 use-after-freeHTTP/2 with upstream forwarding
CVE-2026-121810HTTP/3 use-after-freeHTTP/3 with upstream forwarding
CVE-2026-123634Resolver use-after-freevariable upstreams and SSI/mirror
CVE-2026-118899TLS 1.3 request bodyTLS 1.3 with HTTPS
CVE-2026-113425Mail proxy use-after-freemail proxy using auth_http
CVE-2026-125283alias + try_filesalias, map variable and regex captures
CVE-2026-120967stream client certificate/SNIstream client certificate validation
CVE-2026-123640stream ssl_prereadstream ssl_preread module
CVE-2026-120993stream PROXY protocol v2only some newer 1.31 builds; 1.26.3 not affected

Version caveat: According to nginx and Debian, CVE-2026-120993 affects certain 1.31.x releases, not the older 1.26.3 branch. This table maps functionality; it does not label every Debian 13 installation exploitable against every CVE.

Debian 13 and nginx 1.26.3: why the full package revision matters

Debian commonly backports fixes to stable package versions. Do not decide solely from the upstream number shown by nginx -v. Look at the complete Debian revision and the distribution's CVE tracker. On the morning of 19 November, this host had 1.26.3-3+deb13u10 installed, with the same package still offered as the APT candidate.

dpkg-query -W -f='${binary:Package} ${Version}\n' nginx
apt-cache policy nginx
apt list --upgradable

All three commands are read-only. If needed, sudo apt update refreshes the package lists without installing upgrades.

nginx Debian package revision shown in dpkg-query
The observed Debian package revision: track CVE fixes against the full revision, not just nginx 1.26.3.

Copy-and-paste nginx security checks on Debian 13

1. Validate the nginx configuration

sudo nginx -t

syntax is ok and test is successful indicate valid configuration, not that all vulnerabilities are fixed.

Successful nginx -t syntax check
A successful configuration test prior to any live change.

2. Check for HTTP/2 listeners

sudo nginx -T 2>/dev/null | grep -nE '^[[:space:]]*(listen[[:space:]][^;]*http2|http2[[:space:]]+on;)' || echo 'No HTTP/2 directive found'

No matching HTTP/2 activation was found in the tested configuration. This reduces exposure to HTTP/2-specific issues but says nothing about other services or upstream proxies.

3. Check HTTP/3 and QUIC

sudo nginx -T 2>/dev/null | grep -nE '^[[:space:]]*(listen[[:space:]][^;]*quic|http3[[:space:]]+on;)' || echo 'No HTTP/3/QUIC directive found'

4. Interpret PHP package status correctly

dpkg-query -W -f='${db:Status-Abbrev} ${binary:Package} ${Version}\n' 'php*' 2>/dev/null || true

In dpkg, ii means installed, whereas un means not installed. An unversioned package name is not proof of a functioning PHP runtime. The tested Debian package inventory contained no installed PHP runtime, but containers or manually installed runtimes require separate checks.

5. Inspect HTTPS and TLS protocols

sudo nginx -T 2>/dev/null | grep -nE '^[[:space:]]*(listen|ssl_protocols)[[:space:]]'

Before the temporary morning change, the tested HTTPS configuration enabled TLS 1.3. CVE-2026-118899 can make an nginx worker loop indefinitely while reading a request body over a specially crafted TLS 1.3 connection. An ordinary successful HTTPS response does not rule out the flaw.

6. Inspect unattended security update logs

sudo tail -n 35 /var/log/unattended-upgrades/unattended-upgrades.log

Automatic security updates are enabled through unattended-upgrades on my Debian 13 server. I regularly review update activity and logs.

Logs show when the job ran; the allowed repositories and actual package installs must be checked separately. Automated updates cannot supply a patch that Debian has not published yet.

Mitigation while Debian security packages are pending

A corrected distribution package is the preferred fix. Until one is available, a targeted temporary mitigation may reduce exposure to a specific feature:

TLS configuration after the temporary change: TLSv1.2 in both directives
Verified configuration after the temporary TLS change.
  • HTTP/2: disable exposed HTTP/2 listeners if not needed. CERT-EU recommends this interim mitigation for CVE-2026-123007 and CVE-2026-123633.
  • HTTP/3: disable QUIC/HTTP/3 if affected and not required.
  • TLS 1.3: temporarily remove TLS 1.3 from the effective ssl_protocols settings to mitigate CVE-2026-118899, while retaining TLS 1.2. This is not a recommendation to disable modern TLS permanently.
  • Other features: evaluate mail proxy, resolver and variable upstreams, SSI/mirror, alias/try_files, and stream modules individually.

Avoid blind search and replace on production: a host may have global and per-vhost protocol settings, shared includes and Certbot-managed files. Back up first, make a targeted change, run nginx -t, reload nginx and test each HTTPS service. Certbot updates may overwrite some settings, so recheck after future renewals or changes.

sudo nginx -t
sudo systemctl reload nginx

Observed verification: after the temporary adjustment, a TLS-1.3-only handshake failed (HTTP 000), while a TLS-1.2-only request returned HTTP 200. The same positive and negative tests were repeated on a second HTTPS service. No exploit payload was sent.

TLS 1.3 test rejected after mitigation
TLS 1.3 handshake rejected by the tested local nginx endpoint.
TLS 1.2 still responds with HTTP 200
The same endpoint remains reachable over TLS 1.2.
Second HTTPS service returns HTTP 200 over TLS 1.2
Second HTTPS service remains available over TLS 1.2.

Only safe terminal excerpts are included here. The public article deliberately omits admin routes, local backend ports, internal mappings and complete virtual-host configuration.

Complete custom 404 error page featuring Dennis Hilk in a Kermit shirt
A custom 404 error page rather than unnecessary internal server details. Click the image to view the complete screenshot at its original resolution.

What about the PHP security updates on 19 November?

Additional PHP security releases were scheduled for 19 November. Check the actual release versions at publication time. nginx and PHP are separate components; running nginx does not imply an installed PHP runtime. WordPress and other PHP users should verify PHP-FPM, package origins and application dependencies separately. Even a URL ending in .php can serve static HTML without executing PHP.

Complete WordPress Easter egg page with diagnostics, Dennis Hilk and Kant portraits
My WordPress Easter egg: no WordPress installation, just static HTML and a Kant/Hochkant pun. Click the image to view the complete screenshot at its original resolution.

FAQ: nginx CVEs on Debian 13 in November 2026

Is nginx 1.26.3 automatically unpatched on Debian 13?

No. Debian backports fixes; check the full Debian revision and CVE-specific status. The morning revision deb13u10 was still flagged as vulnerable for several November issues. By evening the corrected deb13u11 was installed on Worldnode.

Does disabling HTTP/2 fix all ten vulnerabilities?

No. It addresses HTTP/2-specific attack paths but not TLS 1.3, HTTP/3, DNS resolver, mail or stream issues.

Why use TLS 1.2 temporarily?

With correct configuration, TLS 1.2 remains viable. Disabling TLS 1.3 here was a temporary mitigation for a specific nginx defect, which can be reverted after installing the corrected package and validating the change. Worldnode restored TLS 1.3 later that evening after installing deb13u11, checking the configuration and testing both protocols on both services.

Do unattended-upgrades guarantee the server is secure?

No. They can only install published packages. Review logs, repository configuration, service reloads and actual exposed features.

How can HTTP/1.1 work with TLS 1.2?

HTTP is an application protocol, while TLS provides encryption. HTTP/1.1 over TLS 1.2 is a normal combination.

Conclusion: verify the real attack surface, then patch

The test found no enabled HTTP/2 or HTTP/3 settings and no installed PHP runtime from Debian packages. The nginx configuration validated successfully. The TLS-1.3-specific attack surface was temporarily disabled and TLS 1.2 remained operational for both tested HTTPS services. Those original workarounds reduced exposure but did not replace the patch that was pending at the time. The corrected Debian package deb13u11 was installed that evening and nginx was confirmed running. TLS 1.3 was subsequently restored: four protocol-specific local requests confirmed HTTP 200 over TLS 1.2 and TLS 1.3 on both services.

Related earlier post: October 2026 Debian 13 nginx security update, with original server logs.

Primary sources and verification date

Checked: 19 November 2026: morning observations, extended with the evening package upgrade, service checks and TLS 1.3 restoration with four local connection tests (CET). Fix status updated against DSA-6642-1; recheck the tracker for later changes. The original findings are supported by terminal screenshots; the later reload and four connection-test results were confirmed by the operator during the follow-up. This is not a third-party vulnerability scan.