nginx2root: Five new nginx vulnerabilities, and how Cloudflare protects origins from the worst of them
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
F5 and nginx.org disclosed ten nginx flaws on November 18, five of them the memory-corruption bugs Xint named nginx2root. The worst, CVE-2026-123007, affects nginx with HTTP/2 enabled since 1.9.5. Cloudflare says origins reachable only through its proxy are shielded from the HTTP/2 and HTTP/3 bugs, but not the mail proxy bug and only partly the resolver bug. Google Cloud says its core load balancing is unaffected. Fixes are in nginx 1.30.7 and 1.31.9. The severity ratings and disclosure count were not verified.
Why it ranked
No. 16 of 118 with a score of 0.74. The panel rated it highest on technical depth (0.95) and practical relevance (0.92), lowest on new information (0.69). The judges disagreed most on new information (spread 0.79), so the story is marked contested. Placed No. 16, No. 5 by score alone: the sixth Security story of the day (−0.060), and close to “Nginx http2 RCE”, No. 1 on Thursday 19 November 2026 (−0.019). The placement terms move stories; they are not part of the score.
- AI judgeJudge 2claude-haiku-5-5
- Major nginx vulnerability disclosure with detailed technical analysis and actionable mitigation; security-focused, substantive, though partly a vendor marketing post promoting its edge protection, and much of its content overlaps with recently covered security stories.
- AI judgeJudge 3gpt-5.6-luna
- A highly technical, actionable analysis of newly disclosed nginx and kernel vulnerabilities, with code-level explanations, testing methodology, mitigations, and exposure guidance. It is substantially promotional because the protection narrative centers on the blinded proxy provider.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.74total under rubric v2.3Contestedjudges differ by 0.79 on new information, 0.69 on promotional
- Significance0.79
- Reader interest0.87
- Audience breadth0.78
- Practical relevance0.92
- Substantiated0.85
- Technical depth0.95
- New information0.69
- Counts against: Promotional0.44
- Counts against: Overclaim0.22
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.75 | 0.80 | 0.82 | 0.79 | 0.07 | +0.24 | +0.190 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.86 | 0.90 | 0.86 | 0.87 | 0.04 | +0.26 | +0.227 |
| Audience breadthHow many people who build technology does it concern? | 0.78 | 0.85 | 0.72 | 0.78 | 0.13 | +0.13 | +0.102 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.95 | 0.90 | 0.90 | 0.92 | 0.05 | +0.22 | +0.202 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.85 | 0.85 | 0.86 | 0.85 | 0.01 | +0.05 | +0.043 |
| Technical depthHow technically substantive is it? | 1.00 | 0.90 | 0.96 | 0.95 | 0.10 | +0.05 | +0.048 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.87 | 0.20 | 0.99 | 0.69 | 0.79 , above the contested threshold | +0.05 | +0.034 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.09 | 0.45 | 0.78 | 0.44 | 0.69 , above the contested threshold | −0.19 | −0.084 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.28 | 0.20 | 0.18 | 0.22 | 0.10 | −0.11 | −0.024 |
| Sum of contributions | +0.737 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.737 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-21/16/"><img src="https://rubric.hrih.si/badge/2026-11-21/16.svg" alt="Ranked #16 on Rubric, 21 Nov 2026" width="245" height="28"></a>Claim check
Claim check: 1 matches source · 1 no source given · 1 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
No source givenDate
F5 and nginx.org disclosed ten nginx vulnerabilities on November 18, 2026, five of which Xint published as nginx2root.
The article gives no link or citation for it.
The article says “On November 18, 2026, F5 and nginx.org disclosed ten vulnerabilities in nginx”
The source says No source to compare with.
Couldn’t checkNumber
F5 rates each of the five nginx2root CVEs High (CVSS 3.1: 8.1) and Critical (CVSS 4.0: 9.2), and notes code execution requires disabling or bypassing ASLR.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “F5 rates each one High (CVSS 3.1: 8.1) and Critical (CVSS 4.0: 9.2”
The source says No passage could be compared.
Source cited by the article: my.f5.com/manage/s/article/K000164058
Matches sourceNumber
Xint's Shodan search on November 10 found 56.7 million hosts matching product:nginx, and of the 11.94 million reporting a version, 98.9% were in the affected range.
The cited source says the same thing.
The article says “found 56.7 million hosts matching product:nginx. Of the 11.94 million that reported a version, 98.9% fell in the affected range”
The source says “As of November 10, 2026, Shodan returned 56.7 million hosts for product:nginx. Of these, 11.94 million (21.1%) reported an identifiable version. Among hosts with an identified version, 98.9% fell within…”
Source cited by the article: xint.io/blog/nginx2root-remote-code-execution
Also covered by
Elsewhere
Elsewhere: HN —
Recorded for context only, checked 21 Nov 2026, 05:47 UTC. It played no part in the ranking.