1. Overview
- Fixed versions were released on November 18, 2026. nginx fixed ten CVEs in 1.30.7 (stable) and 1.31.9 (mainline). The details are on the nginx.org security advisories page and in CHANGES.
- Three are rated major, four medium and three minor. nginx gives a severity of major, medium or minor for each advisory and does not publish CVSS scores. For the memory corruption and use-after-free issues, it describes the impact as a segmentation fault in a worker process, which might have potential other impact.
- No workarounds are given. The advisories do not list configuration workarounds; the fix is to update.
Kyodo News (November 19, 2026, via Yahoo! News Japan) reported that if left unpatched, an outsider could take control of the server and run unauthorized programs. Citing a European research organization, the report said nginx is used by about 60% of sites in Japan, and Japan's National Cybersecurity Office has issued an alert. nginx's own advisories describe the most serious memory corruption issues in terms of worker process crashes and "potential other impact." At the time of writing, we have not seen reports of these vulnerabilities being exploited.
2. The ten vulnerabilities
All are fixed in 1.31.9+ and 1.30.7+ (CVE-2026-120993 is a mainline-only issue fixed in 1.31.9).
| CVE | Severity | Description | Vulnerable versions |
|---|---|---|---|
| CVE-2026-123007 | major | Memory corruption in HTTP/2 flow control (flow-control window overflow) | 1.9.5–1.31.8 |
| CVE-2026-118899 | major | Infinite loop while reading the client request body over TLS 1.3 | 1.13.0–1.31.8 |
| CVE-2026-113425 | major | Use-after-free in the mail proxy module | 0.5.33–1.31.8 |
| CVE-2026-123634 | medium | Use-after-free in the resolver (with the resolver directive, when the same name is resolved in simultaneous subrequests) | 0.6.18–1.31.8 |
| CVE-2026-121810 | medium | Use-after-free in HTTP/3 (occurs if worker_connections were not enough) | 1.25.0–1.31.8 |
| CVE-2026-123633 | medium | Use-after-free in HTTP/2 (occurs if worker_connections were not enough) | 1.19.7–1.31.8 |
| CVE-2026-120967 | medium | In the stream module with SNI, client certificates are verified against the default server's configuration instead of the virtual server selected by SNI | 1.25.5–1.31.8 |
| CVE-2026-120993 | minor | NULL pointer dereference with PROXY protocol v2 and dynamic SSL certificate loading | 1.31.4–1.31.8 (mainline only) |
| CVE-2026-125283 | minor | Buffer overflow with alias and try_files in certain configurations | 0.9.6–1.31.8 |
| CVE-2026-123640 | minor | In the stream ssl_preread module, a malformed ClientHello is interpreted differently | 1.15.2–1.31.8 |
The vulnerable ranges are wide, and some go back to the 0.5 and 0.6 series. Almost any nginx in use today falls within at least one of them.
3. Fixed versions and legacy branches
| Branch | Fixed version | Notes |
|---|---|---|
| Mainline (1.31) | 1.31.9 | Fixes all ten |
| Stable (1.30) | 1.30.7 | CVE-2026-120993 does not apply to 1.30 |
| Legacy (1.28.3 / 1.26.3 / 1.24.0 / 1.22.1) | None | Within the vulnerable ranges; upgrade to 1.30.7 or later |
The nginx.org download page lists 1.28.3, 1.26.3, 1.24.0 and 1.22.1 as legacy versions, and none of them include these fixes. If you install nginx from nginx.org packages or from source, upgrade to 1.30.7 or later (or 1.31.9 or later). Distribution packages may include the fixes without changing the version number, as described in section 5.
4. Check whether you are affected
Version and built-in modules
# Version nginx -v # Build options (built-in modules) nginx -V 2>&1 | tr ' ' '\n' | grep -E 'http_v2|http_v3|mail|stream'
If you see --with-http_v2_module, --with-http_v3_module, --with-mail, --with-stream or --with-stream_ssl_preread_module, that feature is built in. A built-in module does nothing unless your configuration uses it, but you still need to update.
Features used in your configuration
# Dump the full loaded configuration and search for relevant directives
sudo nginx -T 2>/dev/null | grep -nE 'http2|quic|http3|resolver|^\s*mail\s*\{|^\s*stream\s*\{|ssl_preread|ssl_verify_client|proxy_protocol|alias|try_files|worker_connections'| Configuration | Related CVEs |
|---|---|
| listen ... http2 / http2 on; | CVE-2026-123007, CVE-2026-123633 |
| HTTPS with TLS 1.3 enabled | CVE-2026-118899 |
| listen ... quic (HTTP/3) | CVE-2026-121810 |
| resolver | CVE-2026-123634 |
| mail { ... } | CVE-2026-113425 |
| stream { ... } with ssl_verify_client and SNI | CVE-2026-120967 |
| stream { ... } with ssl_preread | CVE-2026-123640 |
| proxy_protocol with dynamic certificate loading (1.31.4–1.31.8) | CVE-2026-120993 |
| alias and try_files in the same location | CVE-2026-125283 |
The HTTP/2 and HTTP/3 use-after-free issues (CVE-2026-123633 and CVE-2026-121810) occur when worker_connections are not enough. Checking the error log for worker_connections are not enough tells you whether you reach the connection limit under heavy traffic.
5. Update
Official nginx.org packages
If you use the nginx.org apt / yum repositories, update the package and confirm that you now have 1.30.7 (stable) or 1.31.9 (mainline).
# Debian / Ubuntu (nginx.org repository) sudo apt update apt-cache policy nginx sudo apt install --only-upgrade nginx # RHEL family / Amazon Linux (nginx.org repository) sudo dnf upgrade nginx # on yum systems: sudo yum update nginx # Confirm nginx -v
Distribution packages
For nginx installed with dnf on Amazon Linux 2023 or with apt on Ubuntu and Debian, each distribution ships fixes on its own schedule. They often backport fixes without changing the version number, so the output of nginx -v alone does not tell you. Check the Amazon Linux Security Center, the Ubuntu CVE tracker or the Debian security tracker for the fixed package version of each CVE, then update.
# Amazon Linux 2023 (repositories are locked to the AMI release, so add --releasever=latest) sudo dnf check-release-update sudo dnf upgrade --releasever=latest nginx # Ubuntu / Debian sudo apt update apt list --upgradable 2>/dev/null | grep nginx sudo apt install --only-upgrade nginx # Installed package version rpm -q nginx # Amazon Linux / RHEL family dpkg -l | grep nginx # Ubuntu / Debian
Containers
If you use the official Docker image, change the base image to nginx:1.30.7 or nginx:1.31.9 (or the updated nginx:stable / nginx:mainline), rebuild your image and redeploy. Updating inside a running container is undone by the next deployment.
# Dockerfile FROM nginx:1.30.7 # If you use the stable tag, pull it again without the cache docker pull nginx:stable docker build --pull --no-cache -t my-nginx . # nginx version in the built image docker run --rm my-nginx nginx -v
For products and images that bundle nginx, such as Kubernetes Ingress controllers, wait for each vendor's fixed release and update.
Test the configuration and restart
# Syntax check sudo nginx -t # The binary was replaced, so restart (reload only re-reads the configuration) sudo systemctl restart nginx # Is the running process using the new binary? (shows "(deleted)" if still old) sudo ls -l /proc/$(cat /run/nginx.pid)/exe nginx -v
systemctl reload only re-reads the configuration and leaves the old binary running. Some packages restart nginx automatically on update, but use the commands above to confirm that the new binary is running. To switch without dropping connections, use nginx's binary upgrade procedure (the USR2 signal). The PID file location depends on your environment.
6. If you run nginx on AWS
What needs updating is nginx that you run yourself. ALB and CloudFront are managed services operated by AWS, not nginx that you update. On AWS, check nginx in places like these.
| Where it runs | What to do |
|---|---|
| EC2 | Update and restart nginx as in section 5. If Auto Scaling launches instances from an AMI, build an updated AMI and update the launch template |
| Containers (ECS / EKS, etc.) | Update the base image, rebuild, and replace the tasks or pods |
| Lightsail | AWS does not update nginx inside your instance; update it inside the instance |
| Elastic Beanstalk | Many platforms use nginx as the proxy. Check the platform release notes and move to a newer platform version through managed platform updates or manually |
With several EC2 instances, Systems Manager Run Command can collect the nginx version from all of them at once.
aws ssm send-command \ --document-name AWS-RunShellScript \ --targets Key=tag:Role,Values=web \ --parameters 'commands=["nginx -v 2>&1","rpm -q nginx || dpkg -l nginx"]' \ --comment "nginx version check"
Related links
We take care of inventories and updates of nginx and OS packages through our AWS Operations Service. For AWS security settings, try our free security assessment.
References
Frequently Asked Questions
QIf I don't use HTTP/2 or HTTP/3, do I still need to update?
Yes. Some of the issues, such as the infinite loop while reading request bodies over TLS 1.3 (CVE-2026-118899), relate to ordinary HTTPS configurations. Updating to 1.30.7 / 1.31.9 or later is more reliable than ruling out each of the ten affected features one by one.
QCan I work around the issues with configuration changes?
The nginx security advisories do not give any workarounds. The fix is to update. Removing features you don't use (mail, stream and so on) from your configuration reduces exposure, but it does not replace updating.
Qnginx -v shows 1.24.0, but it is a distribution package. Am I affected?
Distributions often backport fixes without changing the version number, so the version alone does not tell you. Check the Amazon Linux Security Center or the Ubuntu and Debian security trackers for the fix status and fixed package version of each CVE.
QI use ALB or CloudFront. Do I need to do anything?
ALB and CloudFront are services operated by AWS; they are not nginx that you update. If you run nginx on EC2 or containers behind them, that nginx needs to be updated.
QIs a reload enough after updating?
A reload only re-reads the configuration; the running binary is not replaced. After updating the package, restart nginx or use the binary upgrade procedure to switch to new processes.
