NGINX HTTP/2 vulnerabilities
Passively check NGINX installations for CVE-2026-123007 and CVE-2026-123633 and interpret version, backports, and HTTP/2 configuration.
The NGINX HTTP/2 vulnerabilities check passively assesses discovered NGINX installations on Windows, Linux, and macOS (x64 and Arm64) for CVE-2026-123007 and CVE-2026-123633. It evaluates the installed version, package information, and HTTP/2 configuration. It runs on the device, every 60 minutes by default. It does not execute nginx, send network traffic, attempt exploitation, or change configuration or services.
Prerequisites
- The octoja agent is installed and connected on the device.
- The agent can read the nginx binaries, the package database, and the nginx configuration files.
Steps
- Go to Devices and open the device.
- In the Checks tab, click Add Check → NGINX HTTP/2 vulnerabilities.
- For installations outside the usual directories, add Additional paths.
- Click Add Check.
- After the first run, open the result. Review the per-CVE assessment of each installation and the Coverage gaps.
For many devices, assign the check through a config package.
Settings
The check finds nginx through running processes (including their -c and -p arguments), common installation paths, and PATH. It reads the version and compiled paths from the binary, on Linux the owning package and its changelog (dpkg or rpm), and the configuration including include files.
Results
Both CVEs affect the HTTP/2 module. According to the nginx security advisories and F5 (K000163926, K000163928):
Critical means exposure, not confirmed exploitation. Firewalls, CDNs, and WAFs are not assessed and do not count as proof of safety.
Warning: HTTP/2 counts as off only when the entire configuration, including all includes, could be read. Missing, unreadable, or dynamic includes, a configuration changed after nginx started, and -g startup directives that can change the configuration result in unknown exposure. Common directives such as daemon or master_process are exempt. Container configurations are not read.
FAQ
Why does a distribution package show a warning instead of OK or Critical?
Why does a distribution package show a warning instead of OK or Critical?
Distributions often backport fixes without increasing the upstream version. A changelog entry proves neither a fix (it may describe a revert or partial fix) nor its absence. The check therefore treats vendor builds in the affected range as unknown. Compare the package and version with your distribution's security advisory.
Is worker_connections usage assessed?
Is worker_connections usage assessed?
No. CVE-2026-123633 also requires worker connections to run low at runtime. The check only shows the configured value.
How can I reduce the risk until I can update?
How can I reduce the risk until I can update?
Follow the guidance from F5 and your distribution. Wiz recommends temporarily disabling HTTP/2. Test the change and reload nginx, then run the check again.
See also: Set up alerts for a check
Was this helpful?
More in Antivirus & security
Acronis Cyber Protect AntivirusAntivirus StatusAppLocker Block EventsUser Account AuditStill need help? Ask the team