NGINX HTTP/2 Vulnerability CVE-2026-123007: Protect and Update Your VPS

Tripoli, 19 November 2026. On 18 November, F5 disclosed CVE-2026-123007, a memory-corruption vulnerability in NGINX HTTP/2 flow control. This guide helps Libyan Spider VPS customers identify affected installations, temporarily disable HTTP/2 when necessary, and install the appropriate security update.

Update NGINX promptly. Upstream fixes are available in 1.30.7 (stable) and 1.31.9 (mainline). Ubuntu and AlmaLinux provide backported fixes with different package revisions. Disabling HTTP/2 is a temporary mitigation for the HTTP/2 issues, not a replacement for the full security update.

What is the risk?

Specially crafted HTTP/2 traffic can corrupt worker-process memory and cause a crash. Remote code execution is also possible when address-space layout randomization (ASLR) is disabled or bypassed. No account or user interaction is required. The reported scores are CVSS v4.0: 9.2 (Critical) and CVSS v3.1: 8.1 (High); NGINX uses the severity label “major” for this issue. See the vendor CVE details.

The issue is part of the five-vulnerability group called NGINX2Root. The HTTP/2 mitigation below also addresses exposure to CVE-2026-123633, where applicable. Other flaws in the group involve different NGINX features and still require updates.

Who should check their VPS?

  • Customers running an unpatched NGINX build with HTTP/2 enabled for client connections. CVE-2026-123007 dates back to upstream NGINX 1.9.5; check the fixed release for your branch and your vendor’s package advisory.
  • Customers using NGINX through a control panel, container or third-party repository: use that supplier’s update instructions. The system package may not be the NGINX instance actually serving your website.

These commands are for a typical systemd-based Linux VPS where you administer NGINX. Keep SSH or console access available, back up the active configuration and arrange a brief service interruption for the restart. For a panel-managed or non-standard installation, contact Support before applying generic package or configuration changes.

Step 1: identify the installed build and package

Connect to the VPS using SSH and run:

nginx -v
nginx -V 2>&1 | grep -- --with-http_v2_module

The second command checks whether the build includes HTTP/2 support; it does not prove that HTTP/2 is enabled. Inspect the active configuration in Step 2.

Check your operating system and complete package revision:

cat /etc/os-release

Ubuntu

dpkg-query -W -f='${Package} ${Version}\n' 'nginx*'
apt-cache policy nginx

AlmaLinux

rpm -q nginx
dnf info installed nginx

On AlmaLinux 8 or 9, also check the selected module stream:

dnf module list nginx

Do not judge distribution packages only by nginx -v. A fixed Ubuntu package can still display nginx/1.24.0. Compare the full package revision with the correct release and stream below; version strings from different distributions or streams are not directly comparable.

Step 2: inspect the active HTTP/2 configuration

Use NGINX’s configuration dump so included files outside /etc/nginx are considered. Run this for the executable and configuration used by the serving instance; deployments using -c, containers or a panel may require a different command.

sudo nginx -T 2>&1 | grep -nE '^[[:space:]]*(listen[[:space:]].*http2|http2[[:space:]]+on[[:space:]]*;)'

Matches identify settings to investigate. Review the surrounding active server and HTTP configuration, including inherited settings, non-standard listeners and any additional NGINX instances. If nginx -T reports an error, resolve it before relying on this check. An empty search alone is not a complete security assessment.

Step 3: temporarily disable HTTP/2 if you cannot update now

Most browsers can fall back to HTTP/1.1, but gRPC and other HTTP/2-dependent clients may stop working. Check these dependencies first and coordinate the change if necessary.

Back up each configuration file before editing it. Remove the legacy http2 parameter from every applicable listen directive, including IPv6 listeners:

# Before
listen 443 ssl http2;
listen [::]:443 ssl http2;

# After
listen 443 ssl;
listen [::]:443 ssl;

If your build supports the http2 directive (introduced upstream in 1.25.1), change applicable http2 on; settings to:

http2 off;

Check both the http and server contexts and any explicit overrides. Do not add this directive to older builds that do not support it. With legacy shared listen settings, leaving HTTP/2 enabled on another virtual host on the same address and port can preserve exposure.

Step 4: test and restart NGINX

sudo nginx -t

Proceed only if the configuration test succeeds. Then restart the correct NGINX service so existing workers and connections do not continue using the old configuration:

sudo systemctl restart nginx
sudo systemctl status nginx --no-pager

If the configuration test fails, do not restart. Correct the error or restore the backed-up configuration. A restart can briefly interrupt traffic; check the service and website immediately afterward.

Step 5: test the origin server directly

From a system with an HTTP/2-capable curl build, check HTTPS negotiation. Replace the example hostname:

curl -sS -o /dev/null --http2 -w '%{http_version}\n' https://www.example.com/
  • 1.1: this tested connection negotiated HTTP/1.1.
  • 2: the tested endpoint still offers HTTP/2; check the configuration and the server you reached.
  • A curl error, failed certificate check or 000 is not a successful verification. Check curl -V if curl reports that HTTP/2 is unsupported.

If the hostname is proxied through Cloudflare or another CDN, that test measures the CDN edge. To test an authorized origin while keeping the correct hostname and TLS verification, use its actual address:

curl -sS --resolve www.example.com:443:203.0.113.10 \
  --http2 -o /dev/null -w '%{http_version}\n' https://www.example.com/

Replace both www.example.com occurrences and the documentation-only IP 203.0.113.10. Test each relevant origin, hostname and listener, including IPv6 where used. If origin access is restricted or its certificate requires a private trust chain, ask Support to test through the correct trusted path; do not disable certificate verification.

An HTTP/1.1 result verifies only the tested connection. It does not prove that every listener is mitigated or that the other NGINX2Root flaws are fixed.

Step 6: install the permanent security update

Use the repository that supplies your installed NGINX build. Review the proposed package transaction before confirming it. After the upgrade, test configuration and restart the serving instance.

Ubuntu packages

sudo apt update
sudo apt install --only-upgrade 'nginx*'
sudo nginx -t

If the test succeeds:

sudo systemctl restart nginx
sudo systemctl status nginx --no-pager

Reference package revisions published in USN-9159-1 on 19 November 2026. Install the listed revision or a later vendor security revision for the same Ubuntu release:

Ubuntu releaseFixed package revision
26.101.30.4-7ubuntu1.2
26.04 LTS1.28.3-2ubuntu1.13
24.04 LTS1.24.0-2ubuntu7.20
22.04 LTS1.18.0-6ubuntu14.23
20.04 LTS1.18.0-0ubuntu1.7+esm5 — Ubuntu Pro
18.04 LTS1.14.0-0ubuntu1.11+esm6 — Ubuntu Pro
16.04 LTS1.10.3-0ubuntu0.16.04.5+esm11 — Ubuntu Pro with Legacy Support

Check the installed revision again using the Step 1 commands. Older releases may require an enabled support entitlement; if no fix is offered, check the current Ubuntu tracker and your repository configuration rather than assuming the system is patched.

AlmaLinux packages

sudo dnf clean metadata
sudo dnf upgrade 'nginx*'
sudo nginx -t

If the test succeeds:

sudo systemctl restart nginx
sudo systemctl status nginx --no-pager
rpm -q nginx

Reference builds from the AlmaLinux advisory; use the build for your release and stream, or a later vendor-fixed build in that stream:

Release / streamFixed nginx build
AlmaLinux 8 / nginx:1.24nginx-1.24.0-3.module_el8.10.0+4373+4291aaad.6.alma.4
AlmaLinux 9 / default 1.20nginx-1.20.1-32.el9_9.1.alma.4
AlmaLinux 9 / nginx:1.24nginx-1.24.0-9.module_el9.9.0+356+d723c317.1.alma.4
AlmaLinux 9 / nginx:1.26nginx-1.26.3-10.module_el9.9.0+357+ccfac862.1.alma.2
AlmaLinux 10 / default 1.26nginx-1.26.3-16.el10_3.1.alma.3

Retired streams do not receive these fixes: AlmaLinux 8 nginx:1.14, 1.16, 1.18, 1.20 and 1.22, and AlmaLinux 9 nginx:1.22. Keep the HTTP/2 mitigation in place and plan a tested migration to a supported stream. Changing a module stream is a separate migration; follow the vendor instructions or ask Support rather than blindly resetting production modules.

nginx.org, control-panel and container installations

For nginx.org Open Source packages, confirm 1.30.7 or a later stable security release, or 1.31.9 or a later mainline security release, as appropriate. NGINX Plus customers should use the F5 advisory for their release. Panel-managed builds require the panel vendor’s fix. For containers, rebuild or pull the fixed image and redeploy the actual workload; updating the host package alone does not update an NGINX container.

A normal configuration reload does not load a newly installed NGINX executable. After a package security upgrade, use a full service restart or the vendor’s documented binary-upgrade procedure. Installing an update without activating it leaves old processes running.

Step 7: verify the fix and restore HTTP/2 when ready

Confirm the full installed package revision, a successful restart, the active service state and normal website operation. For multiple instances or containers, verify each serving workload. Once the fixed build is running, you can restore HTTP/2 if needed, test the configuration, restart safely and verify your applications again. Keep the temporary mitigation until the fixed build is confirmed.

Need help?

Contact [email protected] or open a ticket in the Libyan Spider Client Area. Mention “NGINX CVE-2026-123007”, your VPS service, operating-system release, NGINX package revision and whether a control panel or container supplies it. Do not post full configuration dumps or credentials publicly.

Official references

Reviewed on 19 November 2026. Package revisions and vendor guidance can change; follow the linked advisory for your installed release.

Share this:
FacebookXWhatsAppTelegramLinkedInGmailCopy Link
Updated on November 19, 2026
Was this article helpful?

Related Articles

Need Support?
Can't find the answer you're looking for?
Contact Support