# 🚨 NGINX HTTP/2 vulnerabilities: affected versions, distribution patches, and mitigation

**URL:** <https://forum.hhf.technology/t/nginx-http-2-vulnerabilities-affected-versions-distribution-patches-and-mitigation/4916>\
**Category:** 🚨→Security Advisory→🚨\
**Tags:** cve, nginx, security\
**Created:** [November 19, 2026, 4:42am UTC](https://forum.hhf.technology/t/nginx-http-2-vulnerabilities-affected-versions-distribution-patches-and-mitigation/4916 "2026-11-19T04:42:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![hhf.technoloy](https://forum.hhf.technology/user_avatar/forum.hhf.technology/hhf.technoloy/32/68_2.png) [@hhf.technoloy](https://forum.hhf.technology/u/hhf.technoloy)\
**Post date:** [November 19, 2026, 4:42am UTC](https://forum.hhf.technology/t/nginx-http-2-vulnerabilities-affected-versions-distribution-patches-and-mitigation/4916/1 "2026-11-19T04:42:46Z")

</div>

# NGINX HTTP/2 vulnerabilities: affected versions, distribution patches, and mitigation

Two HTTP/2 vulnerabilities can permit unauthenticated remote code execution in NGINX. Upstream fixes are available in **1.30.7 stable** and **1.31.9 mainline**. Distribution packages may contain backported fixes under older version numbers. See the [NGINX security advisories](https://nginx.org/en/security_advisories.html).

This independent summary references [Mattias Geniar’s package-status report](https://ma.ttias.be/nginx-http2-cve-2026-123633-123007/) and the vendor sources linked below.

## Which installations are affected?

HTTP/2 must be enabled. The upstream affected ranges differ:

| Vulnerability | Affected upstream versions | Conditions |
| --- | --- | --- |
| CVE-2026-123007 | 1.9.5–1.31.8 | HTTP/2 flow-control memory corruption; exploitation demonstrated over HTTPS, including static-file servers. |
| CVE-2026-123633 | 1.19.7–1.31.8 | HTTP/2 use-after-free associated with scarce connection slots and reverse-proxy processing. |

Sources: [NGINX affected versions](https://nginx.org/en/security_advisories.html) and [Wiz research](https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities).

Check the binary version and effective configuration locally:

```bash
nginx -v
sudo nginx -T 2>/dev/null | grep -n http2

```

Review matching directives: comments or `http2 off;` do not establish exposure. An externally reachable origin remains relevant even when normal traffic passes through a CDN.

## Distribution package status

**Snapshot:** the source article’s table was checked on **19 November 2026 at 01:58 UTC**. All its distribution entries are represented below. **Debian sid has been annotated with newer tracker information.** Other entries retain the reported snapshot; repository and architecture availability can change.

**Fixed** means a package addressing both CVEs was reported available. **Pending** means work or rollout was underway. **No fix** means none was reported in that snapshot. **Analysis** means the vendor had not confirmed its assessment.

| Distribution / channel | Status | Package or details |
| --- | --- | --- |
| nginx.org packages | Fixed | `1.30.7` stable; `1.31.9` mainline. Reported coverage: Ubuntu 22.04/24.04/26.04; Debian 12/13; RHEL 8/9/10 and rebuilds; SLES 15 SP6+/16; Alpine 3.21–3.24; Amazon Linux 2023. [Supported repositories](https://nginx.org/en/linux_packages.html). |
| Docker official NGINX image | Fixed | `nginx:1.30.7` or `nginx:1.31.9`. [Image tags](https://hub.docker.com/_/nginx). |
| NGINX Plus | Fixes listed; check branch | R33 and 37.x affected. Wiz lists `37.0.7.1`/`37.2.0.1` for CVE-2026-123633 and `37.0.8.1`/`37.3.0.1` for CVE-2026-123007. Choose a release covering both: [F5 advisory 1](https://my.f5.com/manage/s/article/K000163928), [F5 advisory 2](https://my.f5.com/manage/s/article/K000163926). |
| Ubuntu 24.04 LTS | No fix | [Ubuntu tracker](https://ubuntu.com/security/CVE-2026-123007). |
| Ubuntu 22.04 LTS | No fix | [Ubuntu tracker](https://ubuntu.com/security/CVE-2026-123007). |
| Ubuntu 26.04 LTS | No fix | [Ubuntu tracker](https://ubuntu.com/security/CVE-2026-123007). |
| Ubuntu 26.10 | No fix | [Ubuntu tracker](https://ubuntu.com/security/CVE-2026-123007). |
| Ubuntu 20.04 / 18.04 / 16.04 | No fix | Extended security updates require Ubuntu Pro. [Tracker](https://ubuntu.com/security/CVE-2026-123007). |
| Debian 13 trixie | No fix | `1.26.3-3+deb13u10` vulnerable. [Tracker](https://security-tracker.debian.org/tracker/CVE-2026-123007). |
| Debian 12 bookworm | No fix | `1.22.1-9+deb12u10` vulnerable. [Tracker](https://security-tracker.debian.org/tracker/CVE-2026-123007). |
| Debian sid | Updated tracker information | Article snapshot: `1.30.6-4` uploaded, archive availability pending. The [current tracker](https://security-tracker.debian.org/tracker/CVE-2026-123007) lists that version as fixed for CVE-2026-123007; verify [both CVEs](https://security-tracker.debian.org/tracker/CVE-2026-123633) and mirror availability before deployment. |
| Debian forky | No fix | `1.30.6-3` vulnerable. [Tracker](https://security-tracker.debian.org/tracker/CVE-2026-123007). |
| RHEL 9 | No fix | Default package and `nginx:1.24`/`nginx:1.26` streams. [Tracker](https://access.redhat.com/security/cve/cve-2026-123007). |
| RHEL 10 | No fix | [Red Hat tracker](https://access.redhat.com/security/cve/cve-2026-123007). |
| RHEL 8 | No fix | `nginx:1.24` stream. [Tracker](https://access.redhat.com/security/cve/cve-2026-123007). |
| AlmaLinux 10 | Fixed | `2:1.26.3-16.el10_3.1.alma.2`; x86\_64, x86\_64\_v2, aarch64, ppc64le, s390x. [ALSA-2026:A024](https://errata.almalinux.org/10/ALSA-2026-A024.html). |
| AlmaLinux 9 default package | Fixed | `2:1.20.1-32.el9_9.1.alma.3`; x86\_64, aarch64, ppc64le, s390x. [ALSA-2026:A025](https://errata.almalinux.org/9/ALSA-2026-A025.html). |
| AlmaLinux 9 module streams / AlmaLinux 8 | No fix | AlmaLinux 9 `nginx:1.24`/`nginx:1.26` and AlmaLinux 8 had no listed advisory. [Errata](https://errata.almalinux.org/). |
| Amazon Linux 2023 | Fixed | `1.30.7-1.amzn2023.0.1`; x86\_64, aarch64. [ALAS2023-2026-3494](https://alas.aws.amazon.com/AL2023/ALAS2023-2026-3494.html). |
| Amazon Linux 2 | Pending | `nginx1` extra awaiting fixes for both CVEs. |
| Alpine 3.24 | Fixed | `1.30.7-r0`. |
| Alpine edge | Fixed | `1.30.7-r0`. [Packages](https://pkgs.alpinelinux.org/packages?name=nginx). |
| Alpine 3.23 / 3.22, x86\_64 | Fixed | `1.28.3-r8`, backported fixes. [Security database](https://secdb.alpinelinux.org/v3.23/main.json). |
| Alpine 3.23 / 3.22, other architectures | Pending | Fix recorded in `1.28.3-r8`; aarch64 repositories still reported `1.28.3-r7`. |
| Alpine 3.21 | No fix | `1.26.3-r3` vulnerable. |
| Arch Linux, extra | Fixed | [`nginx 1.30.7-1`](https://archlinux.org/packages/extra/x86_64/nginx/); [`nginx-mainline 1.31.9-1`](https://archlinux.org/packages/extra/x86_64/nginx-mainline/). |
| Fedora 45 / 44 / 43 | No fix | `1.30.6` reported vulnerable. |
| SLES 15 SP7 / 16.0 / 16.1; openSUSE Leap 16.0 / 16.1 | Analysis | [Vendor assessment pending](https://www.suse.com/security/cve/CVE-2026-123007.html). |
| openSUSE Tumbleweed | No fix | `1.31.8-1.1` reported vulnerable. |

Snapshot-only entries and rollout details are attributed to [the original report](https://ma.ttias.be/nginx-http2-cve-2026-123633-123007/). Consult the vendor’s notices for **both** CVEs before treating an installation as patched.

## Apply and verify the fix

Install a vendor-confirmed patched package, then validate the configuration and restart the service. A configuration reload alone does not replace the running executable. See [NGINX process control](https://nginx.org/en/docs/control.html).

On systemd installations, after updating:

```bash
sudo nginx -t && sudo systemctl restart nginx

```

Alpine uses `sudo rc-service nginx restart`. For containers, deploy the patched image and recreate the container.

If using [nginx.org](http://nginx.org) packages, follow the [official repository instructions](https://nginx.org/en/linux_packages.html). Back up configuration and check site includes and dynamic-module compatibility before switching package sources.

Check the full installed package version against your vendor advisory; an older upstream version may already include a backport. [Red Hat explains this distinction](https://access.redhat.com/security/cve/cve-2026-123007).

## Temporary workaround: disable HTTP/2

On NGINX 1.25.1 or later, disable HTTP/2 in each applicable server block and remove legacy `http2` parameters from `listen` directives:

```nginx
server {
    listen 443 ssl;
    http2 off;
    # Keep the remaining site configuration.
}

```

On older versions, remove `http2` from every applicable `listen` directive. Review all virtual hosts sharing the listening address. See the [HTTP/2 module documentation](https://nginx.org/en/docs/http/ngx_http_v2_module.html) and [Wiz mitigation guidance](https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities).

Test, reload, and allow the old workers to exit. On systemd:

```bash
sudo nginx -t && sudo systemctl reload nginx
curl --http2 -sS -o /dev/null -w '%{http_version}\n' https://example.com/

```

Replace the example URL with your endpoint. With an HTTP/2-capable curl, `1.1` indicates fallback for that endpoint. Test each exposed origin and hostname; a CDN-facing check only tests the CDN connection.

Disabling HTTP/2 is temporary. The same releases address additional issues, including HTTP/3 CVE-2026-121810, so install the security updates even after applying the workaround. Re-enable HTTP/2 once the patched deployment is verified. [NGINX advisories](https://nginx.org/en/security_advisories.html).

---

<div class="post-metadata">

**Author:** ![hhf.technoloy](https://forum.hhf.technology/user_avatar/forum.hhf.technology/hhf.technoloy/32/68_2.png) [@hhf.technoloy](https://forum.hhf.technology/u/hhf.technoloy)\
**Post date:** [November 19, 2026, 5:07am UTC](https://forum.hhf.technology/t/nginx-http-2-vulnerabilities-affected-versions-distribution-patches-and-mitigation/4916/2 "2026-11-19T05:07:17Z")

</div>

Pinned globally on November 19, 2026, 5:07am UTC


