Ruby2Shell (GHSA-34m4-m9fh-gqp5)
6 comments · ruby, security
- Comments5
6 comments · ruby, security
Story details from Lobsters ↗ · linked article on verialabs.com.
Ruby2Shell (GHSA-34m4-m9fh-gqp5) was first seen on Lobsters · Hottest on Nov 19, 2026. Since then it has appeared in 35 checks on 2 different days. Its best position was #4 of 25, reached on Nov 19, 14:22 UTC. It is #7 right now, holding steady at #7 over the last 6 checks. The same link also trended on Hacker News, which raises its cross-platform score.
Position on Lobsters · Hottest at every check (lower is better).
Best rank per day (UTC).
▲ as reported by Lobsters.
| List | Best | Days | Checks | Last seen |
|---|---|---|---|---|
| Lobsters · Hottest | #4 | 2 | 35 | |
| YHacker News · Front page Ruby2ßhell: Pre-authentication RCE on stock Rails | same link | |||
A few top-level comments from Lobsters, shortened. Read the full thread on Lobsters.
Ruby bends over backwards to hide the details of string encoding from the user, and to interpret them in a way that keeps control flow going. Correct Ruby string handling entails a lot of `force_encoding!` at interface boundaries. So I think if you specified one of the affected encodings in something like a…
> UTF-8 strings take a different code path and are not affected. So, it is pretty much a nothingburger?
No, it's very real, because Rack allow to send strings in arbitrary encodings via multipart chunks. This behavior is likely to be removed from future versions of rack (currently in review). I already added a feature in Rails to monkey patch it out. Now this only allow triggering a single byte of overflow, but it's…
Archived daily, weekly and monthly lists that include this entry.
Yes. As of Nov 20, 03:52 UTC it is #7, holding steady at #7 over the last 6 checks.
#4 on Lobsters · Hottest, on Nov 19, 14:22 UTC. Trendoday checks this list every 30 minutes.
It was first seen on Nov 19, 2026 and has been on the list on 2 days (35 checks) since.