DEV Community

TinyMomentum1
TinyMomentum1

Posted on

I built a browser-based checker for CVE-2026-123007 in NGINX

I started building this checker after looking at CVE-2026-123007 on my own Ubuntu server. nginx -V showed that the binary was built with HTTP/2 support. In the configuration dumped by nginx -T, the HTTPS listener used listen 443 ssl;, and I couldn’t find an HTTP/2 enablement directive.

That left a separate question. Had Ubuntu patched the package I was running? The NGINX banner said 1.24.0, while the installed package version was 1.24.0-2ubuntu7.19. I needed the full package version to look up Ubuntu’s patch status.

What the checker shows

The result separates the HTTP/2 configuration finding from the package patch status. For my server, that meant the pasted configuration showed no HTTP/2 enablement, while the installed package was listed as affected at the time I checked.

The tool reads version, build and configuration details locally in the browser. It checks Ubuntu 24.04 LTS package versions against synchronized Canonical advisory data and shows when that data was last checked. It doesn’t connect to your server, so the result depends on the configuration you provide.

Try it

Open TheBinaryKit Security and click Load example to see a result using sample data.

If you run NGINX on Ubuntu, I’d like to know whether the report makes the next step clear, especially when it finds no HTTP/2 enablement but the package still needs an update.

AI helped draft this post based on my own troubleshooting notes.

Top comments (1)

Collapse
 
alexcodebytes profile image
Oleksandr •

I like that the checker separates configuration exposure from package vulnerability status. Having HTTP/2 support compiled into the binary doesn't automatically mean it's enabled for a particular listener, and the reverse is also important: a configuration that doesn't expose HTTP/2 doesn't mean the installed package is patched. Showing the full Ubuntu package version alongside the configuration analysis makes the result much more actionable than a simple version check. The local-browser approach is also a sensible choice for a security diagnostic tool.