Ruby2Shell (GHSA-34m4-m9fh-gqp5)
Comments on “Ruby2Shell (GHSA-34m4-m9fh-gqp5)”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
Veria Labs disclosed GHSA-34m4-m9fh-gqp5, a one-byte heap overflow in Ruby's case mapping for single-byte encodings such as ISO-8859 and Windows-125x. Upcasing ß writes two bytes but the loop checks for one, so 21 of them overrun a buffer sized at input length plus 20. Rails and classic Sinatra are reachable by default. Fixed in Ruby 3.3.14, 3.4.13 and 4.0.10. Per Veria, GitLab, GitHub Enterprise Server and Chatwoot have no fix yet; a Rails remote code execution proof of concept is due 25 November. Most claims here come from Veria alone.
Why it ranked
No. 2 of 140 with a score of 0.79. The panel rated it highest on practical relevance (0.91) and new information (0.91), lowest on audience breadth (0.75).
- AI judgeJudge 2claude-haiku-5-5
- Major advisory with a concrete one-byte heap overflow in Ruby's case-conversion code, affected versions, fixes and vendor status; highly actionable for builders, with a PoC pending and technical detail but limited full root-cause depth.
- AI judgeJudge 3gpt-5.6-luna
- A technically detailed Ruby heap-overflow advisory affects Rails, Sinatra, and bundled enterprise products, with clear versions and mitigations. It is highly actionable and novel, though the promised remote-code-execution demonstration is not yet available, making the title somewhat ahead of the evidence.
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.76
- Reader interest0.87
- Audience breadth0.75
- Practical relevance0.91
- Substantiated0.78
- Technical depth0.89
- New information0.91
- Counts against: Promotional0.04
- Counts against: Overclaim0.34
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.72 | 0.82 | 0.76 | 0.10 | +0.24 | +0.182 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.81 | 0.90 | 0.90 | 0.87 | 0.09 | +0.26 | +0.226 |
| Audience breadthHow many people who build technology does it concern? | 0.74 | 0.80 | 0.72 | 0.75 | 0.08 | +0.13 | +0.098 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.94 | 0.92 | 0.88 | 0.91 | 0.06 | +0.22 | +0.201 |
| 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.75 | 0.80 | 0.78 | 0.78 | 0.05 | +0.05 | +0.039 |
| Technical depthHow technically substantive is it? | 0.96 | 0.80 | 0.90 | 0.89 | 0.16 | +0.05 | +0.044 |
| 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.05 | 0.03 | 0.03 | 0.04 | 0.02 | −0.19 | −0.007 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.21 | 0.25 | 0.55 | 0.34 | 0.34 | −0.11 | −0.037 |
| Sum of contributions | +0.792 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.792 | ||||||
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-20/2/"><img src="https://rubric.hrih.si/badge/2026-11-20/2.svg" alt="Ranked #2 on Rubric, 20 Nov 2026" width="238" height="28"></a>Claim check
Claim check: 1 matches source · 7 no source given. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
No source givenVersion
The Ruby case-mapping bug affects Ruby 4.0.0 to 4.0.9, 3.4.0 to 3.4.12 and 3.3.0 to 3.3.13, fixed in 4.0.10, 3.4.13 and 3.3.14 respectively.
The article gives no link or citation for it.
The article says “Upgrade Ruby to a fixed release: 3.3.14, 3.4.13 or 4.0.10”
The source says No source to compare with.
No source givenDate
The vulnerable case-mapping loop has been present since Ruby 2.4.0, affecting all releases back to 2.4.0 in series 3.2 and older, which are end-of-life.
The article gives no link or citation for it.
The article says “The same loop is in several ISO-8859 and Windows-125x encodings and has been there since Ruby 2.4.0”
The source says No source to compare with.
No source givenNumber
The output buffer is allocated as the input length plus 20 bytes, and each ß adds one byte, so an input with 21 of them overflows the buffer by one byte.
The article gives no link or citation for it.
The article says “The output buffer is allocated as the input length plus 20 bytes. Each ß adds one byte to the output, so an input with 21 of them overflows the buffer…”
The source says No source to compare with.
Matches sourceCausal conclusion
The bug is caused by the loop bounds-checking only one byte (to < to_end) while upcasing ß writes two bytes (SS), producing a heap overflow.
The cited source says the same thing.
The article says “Upcasing it writes two bytes, SS, but the loop only bounds-checks one (to < to_end”
The source says “while (*pp < end && to < to_end) { | | | 268 | + while (*pp < end && to_end - to > 1”
Source cited by the article: github.com/ruby/ruby/commit/d582f8f13d700d8e39714d3a8f11eb4bd2bc69f0
No source givenGeneralization
UTF-8 strings take a different code path and are not affected by the bug.
The article gives no link or citation for it.
The article says “UTF-8 strings take a different code path and are not affected”
The source says No source to compare with.
No source givenNumber
GitLab 19.6.0 and earlier, GitHub Enterprise Server 3.22.5 and earlier, and Chatwoot 4.20.0 and earlier are vulnerable with no fixed release yet.
The article gives no link or citation for it.
The article says “Products marked Vulnerable have no fixed release yet: every current version is vulnerable”
The source says No source to compare with.
No source givenGeneralization
Rails and Sinatra (classic style) are affected in their default configuration on an affected Ruby.
The article gives no link or citation for it.
The article says “The bug is reachable from the following frameworks in their default configuration”
The source says No source to compare with.
No source givenFirst, only or fastest
Veria Labs found the vulnerability independently and was the first to demonstrate remote code execution.
The article gives no link or citation for it.
The article says “Veria Labs found this vulnerability independently and was the first to demonstrate remote code execution”
The source says No source to compare with.
Also covered by
Elsewhere
Elsewhere: HN 391 pts, front page
Recorded for context only, checked 20 Nov 2026, 05:47 UTC. It played no part in the ranking.