Brotli CVE-2026-111497 reaches stock WordPress through pingbacks
Comments on “Brotli CVE-2026-111497 reaches stock WordPress through pingbacks”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
Patchstack reports that CVE-2026-111497, an out-of-bounds write in Google's Brotli decoder, is reachable on a default WordPress install. An unauthenticated pingback to xmlrpc.php makes WordPress fetch an attacker's URL, and libcurl decodes the Brotli reply. Public tooling only crashes PHP workers, and no public chain gives code execution on PHP. The fix is the OS Brotli package, not a WordPress update; the wordpress:latest Docker image was still vulnerable on October 30. Several details, including the CVSS 9.2 score and CISA listing, were not independently verified.
Why it ranked
No. 2 of 95 with a score of 0.79. The panel rated it highest on practical relevance (0.94) and technical depth (0.91), lowest on audience breadth (0.66).
- AI judgeJudge 2claude-haiku-5-5
- Exploited, widely deployed library flaw reachable unauthenticated via WordPress pingback; concrete detection, mitigation and package-revision guidance, with strong technical detail and cited sources.
- AI judgeJudge 3gpt-5.6-luna
- A highly actionable vulnerability analysis linking a Brotli decoder flaw to default WordPress behavior, with exploit conditions, package-version caveats, mitigations, testing, and detection guidance. It is broad security news, though evidence relies mainly on cited third parties.
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.79total under rubric v2.3
- Significance0.72
- Reader interest0.88
- Audience breadth0.66
- Practical relevance0.94
- Substantiated0.76
- Technical depth0.91
- New information0.91
- Counts against: Promotional0.03
- Counts against: Overclaim0.25
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.65 | 0.72 | 0.78 | 0.72 | 0.13 | +0.24 | +0.172 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.82 | 0.88 | 0.93 | 0.88 | 0.11 | +0.26 | +0.228 |
| Audience breadthHow many people who build technology does it concern? | 0.63 | 0.78 | 0.58 | 0.66 | 0.20 | +0.13 | +0.086 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.95 | 0.94 | 0.91 | 0.94 | 0.04 | +0.22 | +0.206 |
| 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.68 | 0.78 | 0.83 | 0.76 | 0.15 | +0.05 | +0.038 |
| Technical depthHow technically substantive is it? | 1.00 | 0.86 | 0.88 | 0.91 | 0.14 | +0.05 | +0.046 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.85 | 0.90 | 0.98 | 0.91 | 0.13 | +0.05 | +0.046 |
| 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.04 | 0.03 | 0.03 | 0.03 | 0.01 | −0.19 | −0.006 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.37 | 0.20 | 0.18 | 0.25 | 0.19 | −0.11 | −0.028 |
| Sum of contributions | +0.787 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.787 | ||||||
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-10/2/"><img src="https://rubric.hrih.si/badge/2026-11-10/2.svg" alt="Ranked #2 on Rubric, 10 Nov 2026" width="238" height="28"></a>Claim check
Claim check: 2 matches source · 5 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.
Matches sourceCausal conclusion
CVE-2026-111497, a memory bug in Google's Brotli decoder, can be triggered on a default WordPress install by anyone who sends a pingback to xmlrpc.php.
The cited source says the same thing.
The article says “can be triggered on a default WordPress install by anyone who sends a pingback to xmlrpc.php”
The source says “One unauthenticated POST to xmlrpc.php can take down a PHP worker on a stock WordPress install, and there is nothing unusual about the request that does it”
Source cited by the article: patchstack.com/articles/wordpress-doesnt-ship-brotli-its-still-exposed-to-cve-2026-111497
Couldn’t checkNumber
CVE-2026-111497 has a CVSS score of 9.2, scored by Google, and affects Brotli 1.0.3 through 1.2.0.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “Severity CVSS 9.2, scored by Google”
The source says No passage could be compared.
Source cited by the article: nvd.nist.gov/vuln/detail/cve-2026-111497
No source givenVersion
Brotli 1.0.10, 1.1.1 and 1.2.1 were released with the fix on October 21, 2026.
The article gives no link or citation for it.
The article says “Brotli 1.0.10, 1.1.1 and 1.2.1 (October 21, 2026); Debian and Ubuntu backport under 1.1.0”
The source says No source to compare with.
No source givenDate
CISA added CVE-2026-111497 to its Known Exploited Vulnerabilities catalog on October 27, 2026, with a November 10 federal deadline.
The article gives no link or citation for it.
The article says “October 27, 2026: CISA adds the CVE to its Known Exploited Vulnerabilities catalog with a November 10 federal deadline”
The source says No source to compare with.
Matches sourceNumber
As of Patchstack's October 30 post, the official wordpress:latest Docker image still installed a vulnerable libbrotli1.
The cited source says the same thing.
The article says “the official wordpress:latest Docker image still installed a vulnerable libbrotli1”
The source says “wordpress:latest still installs a vulnerable libbrotli1 today”
Source cited by the article: patchstack.com/articles/wordpress-doesnt-ship-brotli-its-still-exposed-to-cve-2026-111497
No source givenNumber
A lab write-up dated October 27 triggered the bug through pingback and recorded a killed worker and a worker stuck at 100% CPU from a payload under a hundred bytes, with no code execution.
The article gives no link or citation for it.
The article says “recorded a killed worker and a worker stuck at 100% CPU from a payload of under a hundred bytes, with no code execution included”
The source says No source to compare with.
No source givenFirst, only or fastest
No public chain achieves code execution against PHP under Apache or PHP-FPM, though working shells exist against stock Node.js and Bun builds.
The article gives no link or citation for it.
The article says “working shells exist against stock Node.js and Bun builds, and no public chain targets PHP under Apache or PHP-FPM”
The source says No source to compare with.
No source givenCausal conclusion
Passing decompress => false to the WordPress HTTP API does not prevent libcurl from decoding Brotli responses, because that setting only governs what WordPress does with an already-unpacked body.
The article gives no link or citation for it.
The article says “Passing decompress => false to the HTTP API does not help; that only governs what WordPress does with a body libcurl has already unpacked”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 1 pts, not on front page
Recorded for context only, checked 10 Nov 2026, 05:47 UTC. It played no part in the ranking.