CVE-2026-123007 nginx2root Patch Checker
nginx2root-check combines an accounting-only HTTP/2 test with package, process and validated configuration-on-disk evidence for CVE-2026-123007.
Read how the checker was developed and calibrated for the reasoning behind the safety boundary and the limitations of version-only checks.
Safety boundary
The checker starts the installed nginx executable with a temporary configuration on a numeric loopback address.
It does not target a remote endpoint, reload production nginx, crash a worker, disclose memory or execute a command.
Only run it on a system you own or are explicitly authorised to test.
Requirements
- Linux with
/proc. - Python 3.9 or newer (Ubuntu 20.04’s stock Python 3.8 is not supported).
- A running nginx installed on the host.
- Root access to inspect every process and executable.
Run
git clone https://github.com/SamJUK/nginx2root-check.git
cd nginx2root-check
sudo ./nginx2root-check \
--acknowledge-owned-system I-AM-AUTHORIZED
Use JSON output for automation:
sudo ./nginx2root-check \
--acknowledge-owned-system I-AM-AUTHORIZED \
--json
This excerpt shows the top-level result and probe evidence, with the full schema_version, audit, host paths and PIDs omitted:
{
"cve": "CVE-2026-123007",
"outcome": "PATCHED",
"reason": "the active sequence was rejected and every running binary maps to a fixed build",
"probe": {
"control_bytes": 65535,
"outcome": "NO_OVER_CREDIT_OBSERVED",
"production_pids_unchanged": true
}
}
Results
| Exit | Result | Meaning |
|---|---|---|
0 | PATCHED | The active sequence was rejected and every running binary maps to a supported fixed build. |
1 | VULNERABLE | The installed binary accepted over-credit; configuration on disk also enables HTTP/2 when that can be read. |
2 | INCONCLUSIVE | The active result, process mapping, configuration or package provenance is incomplete or contradictory. |
A negative active result is never accepted as patch evidence on its own.
Ansible
The repository includes docs/ansible.md, with tasks that copy the checker to a temporary directory, capture the JSON evidence and fail unless the combined result is PATCHED.
Copy the tasks into a playbook for your inventory, run one canary host first, then widen the batch.
Calibration
The isolated differential uses nginx 1.31.8 as the vulnerable positive control and nginx 1.31.9 as the fixed control.
The calibration requires Docker:
tests/docker-differential.sh
It publishes no ports, uses no host networking and removes only its own labelled containers.
Limitations
The first release recognises Ubuntu security revisions and the fixed upstream stable and mainline boundaries documented in the repository.
Other distributions, NGINX Plus, unmanaged binaries, containers, chroots and replaced (deleted) executables fail closed as INCONCLUSIVE.
The checker verifies that the running executable still matches its owning dpkg package and treats a mismatch as inconclusive.
The configuration check runs a package-verified nginx with -T as the stripped-down test account and returns inconclusive if that account cannot validate the files on disk.
It cannot prove existing workers reloaded a recent change, so configured-off HTTP/2 is not reported as a proven mitigation.
Ubuntu Noble 1.24.0-2ubuntu7.20 is deliberately inconclusive because fleet validation produced conflicting active results from byte-identical binaries.
Read the implementation and provenance notes before using the result as deployment evidence.