Finding and attribution
The affected configuration enables HTTP/3 and forwards requests to an upstream server. NGINX lists upstream severity as medium. Researcher-reported code-execution demonstrations are distinct from the upstream severity label; no exploitation-in-the-wild finding is asserted here.
What to update · NGINX Open Source · NGINX Open Source upstream release branches
Affected versions not confirmed in this summary.
Fixed in: 1.31.9 · 1.30.7
Action: Use the upstream fixed release for the relevant branch; consult distribution guidance for backported packages.
The upstream NGINX security list identifies Open Source 1.31.9 and 1.30.7 as fixed. This entry does not establish NGINX Plus, distribution backport or installed-patch status.
Advisory / fix evidence · checked 21 Nov 2026
Product: NGINX Open Source. AI system: Xint autonomous scanning platform (model/version not disclosed). Team / organization: Xint.
CVE identifiers: CVE-2026-121810.
AI and human contribution (source account): Xint includes this CVE among four findings from a fully automated scan without human guidance. Its first-party account identifies the platform as AI-powered; underlying model details are not stated. Researchers handled validation and disclosure.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: Public vendor disclosure; the reviewed sources do not establish discovery-time zero-day or pre-release status.
Remediation status: fix documented.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 18 Nov 2026. AI attribution dated 18 Nov 2026. Sources checked 21 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: Not available · no assessment established here. Documented technical effects: Not available.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
No source-backed CVSS assessment is established in this catalog.
Technical effects, prerequisites and exploitation evidence are not established here. Missing evidence does not establish absence of exploitation.