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.
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.
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
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
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
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
000is not a successful verification. Checkcurl -Vif 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.
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 release | Fixed package revision |
|---|---|
| 26.10 | 1.30.4-7ubuntu1.2 |
| 26.04 LTS | 1.28.3-2ubuntu1.13 |
| 24.04 LTS | 1.24.0-2ubuntu7.20 |
| 22.04 LTS | 1.18.0-6ubuntu14.23 |
| 20.04 LTS | 1.18.0-0ubuntu1.7+esm5 — Ubuntu Pro |
| 18.04 LTS | 1.14.0-0ubuntu1.11+esm6 — Ubuntu Pro |
| 16.04 LTS | 1.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 / stream | Fixed nginx build |
|---|---|
| AlmaLinux 8 / nginx:1.24 | nginx-1.24.0-3.module_el8.10.0+4373+4291aaad.6.alma.4 |
| AlmaLinux 9 / default 1.20 | nginx-1.20.1-32.el9_9.1.alma.4 |
| AlmaLinux 9 / nginx:1.24 | nginx-1.24.0-9.module_el9.9.0+356+d723c317.1.alma.4 |
| AlmaLinux 9 / nginx:1.26 | nginx-1.26.3-10.module_el9.9.0+357+ccfac862.1.alma.2 |
| AlmaLinux 10 / default 1.26 | nginx-1.26.3-16.el10_3.1.alma.3 |
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.
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
- F5 advisory K000163926
- NGINX security advisories
- Ubuntu CVE-2026-123007 tracker
- Ubuntu security notice USN-9159-1
- AlmaLinux NGINX2Root advisory and package revisions
- NGINX HTTP/2 module documentation
- NGINX command-line options
Reviewed on 19 November 2026. Package revisions and vendor guidance can change; follow the linked advisory for your installed release.