nodejs/node v22.23.5
Comments on “nodejs/node v22.23.5”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
Node.js shipped coordinated security releases for its 22.x, 24.x and 26.x lines (v22.23.5, v24.22.3, v26.13.1). The 22.x notes list 17 CVEs: eight High, six Medium, three Low. Most fixes are in http2 and TLS, covering stream and buffer lifetime, SNI changes on resumption, and mTLS resumption. The 24.x and 26.x notes add a High-rated remotely reachable TLS server crash that the 22.x notes omit. Teams running public HTTP/2 or TLS servers should upgrade. The notes give titles and severities, not exploit detail.
Why it ranked
No. 17 of 106 with a score of 0.72. The panel rated it highest on new information (0.92) and practical relevance (0.86), lowest on technical depth (0.57). Placed No. 17, No. 8 by score alone: the seventh Security story of the day (−0.080). The placement terms move stories; they are not part of the score.
- AI judgeJudge 2claude-haiku-5-5
- Security release of a widely used runtime with many high-severity CVEs in HTTP/2 and TLS; practically actionable for builders, though it is a changelog with limited technical explanation.
- AI judgeJudge 3gpt-5.6-luna
- A primary Node.js security release fixes numerous high- and medium-severity HTTP/2, TLS, permission, and credential-leak issues, making it actionable for Node maintainers and users, though the changelog offers limited exploit or remediation detail.
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.72total under rubric v2.3
- Significance0.65
- Reader interest0.70
- Audience breadth0.73
- Practical relevance0.86
- Substantiated0.81
- Technical depth0.57
- New information0.92
- Counts against: Promotional0.04
- Counts against: Overclaim0.07
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.73 | 0.55 | 0.68 | 0.65 | 0.18 | +0.24 | +0.157 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.69 | 0.70 | 0.72 | 0.70 | 0.03 | +0.26 | +0.183 |
| Audience breadthHow many people who build technology does it concern? | 0.69 | 0.80 | 0.70 | 0.73 | 0.11 | +0.13 | +0.095 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.91 | 0.90 | 0.78 | 0.86 | 0.13 | +0.22 | +0.190 |
| 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.83 | 0.70 | 0.90 | 0.81 | 0.20 | +0.05 | +0.040 |
| Technical depthHow technically substantive is it? | 0.56 | 0.60 | 0.55 | 0.57 | 0.05 | +0.05 | +0.028 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.87 | 0.90 | 0.98 | 0.92 | 0.11 | +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.06 | 0.03 | 0.02 | 0.04 | 0.04 | −0.19 | −0.007 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.11 | 0.10 | 0.01 | 0.07 | 0.10 | −0.11 | −0.008 |
| Sum of contributions | +0.724 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.724 | ||||||
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-12/17/"><img src="https://rubric.hrih.si/badge/2026-11-12/17.svg" alt="Ranked #17 on Rubric, 12 Nov 2026" width="245" height="28"></a>Claim check
Claim check: 1 matches source · 1 no source given · 6 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 givenVersion
Node.js v22.23.5 is a security release.
The article gives no link or citation for it.
The article says “This is a security release”
The source says No source to compare with.
Matches sourceVersion
Node.js v22.23.5 updates llhttp to version 9.4.4.
The cited source says the same thing.
The article says “deps: update llhttp to 9.4.4 (Antoine du Hamel”
The source says “project(llhttp VERSION 9.4.4”
Source cited by the article: github.com/nodejs/node/commit/554fff40f0
Couldn’t checkVersion
Node.js v22.23.5 updates sqlite to version 3.54.1.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “deps: update sqlite to 3.54.1 (Node.js GitHub Bot”
The source says No passage could be compared.
Source cited by the article: github.com/nodejs/node/commit/6577cbf231
Couldn’t checkCausal conclusion
Node.js v22.23.5 fixes a High severity issue by releasing http2 headers when a stream is removed.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “http2: release headers when a stream is removed (Matteo Collina) – High”
The source says No passage could be compared.
Source cited by the article: github.com/nodejs/node/commit/9bce421783
Couldn’t checkCausal conclusion
Node.js v22.23.5 fixes a High severity issue by preventing nested parser execution from empty writes in tls and http.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “tls,http: prevent nested parser execution from empty writes (Matteo Collina) – High”
The source says No passage could be compared.
Source cited by the article: github.com/nodejs/node/commit/c841c6c7f1
Couldn’t checkCausal conclusion
Node.js v22.23.5 disables TLS resumption for mTLS with no session id context, rated High severity.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “tls: disable resumption for mTLS with no session id context (Tim Perry) – High”
The source says No passage could be compared.
Source cited by the article: github.com/nodejs/node/commit/06af164d09
Couldn’t checkCausal conclusion
Node.js v22.23.5 redacts proxy credentials in invalid proxy URL errors, rated Medium severity.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “http: redact proxy credentials in invalid proxy URL errors (Matteo Collina) – Medium”
The source says No passage could be compared.
Source cited by the article: github.com/nodejs/node/commit/cd18f6bdff
Couldn’t checkCausal conclusion
Node.js v22.23.5 stops recursive fs.watch from leaking denied descendants under the permission model, rated Low severity.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “permission: do not leak denied descendants in recursive fs.watch (RafaelGSS) – Low”
The source says No passage could be compared.
Source cited by the article: github.com/nodejs/node/commit/5c9eed3b1e
Also covered by
Elsewhere
Elsewhere: HN —
Recorded for context only, checked 12 Nov 2026, 05:47 UTC. It played no part in the ranking.