Seven are rated high, including an account takeover through OAuth2 auto-linking and fork workflows that receive repository secrets. Every release up to 28.2.0 is affected; there is no backport line.
Ruby 4.0.10, 3.4.13 and 3.3.14 fix seven regex and string flaws with RCE PoCs
EditorialBy TrustList Editorial
Ruby core released 4.0.10, 3.4.13 and 3.3.14 on 18 November to fix seven memory-safety flaws in the regular expression engine and string case conversion; it knows of PoCs that reach code execution. Ruby 3.2 and earlier get no fix.
- Cybersecurity
- Application Security
- Web Security
About Ruby 4.0.10, 3.4.13 and 3.3.14 fix seven regex and string flaws with RCE PoCs
Ruby 4.0.10, 3.4.13 and 3.3.14 fix seven regex and string flaws with RCE PoCs
18 November 2026: The Ruby core team has released Ruby 4.0.10, 3.4.13 and 3.3.14 to fix seven vulnerabilities in the language's regular expression engine and in string case conversion. The advisory says the team is aware of proofs of concept showing that some of them can be used to trigger remote code execution, and it strongly recommends upgrading.
Not yet independently verified. This rests on the Ruby project's own advisory of 18 November 2026, read on 19 November. CVE identifiers had been requested but not assigned when it was published, so the flaws are named by their GitHub Security Advisory identifiers. Whether an application is exposed depends on whether it compiles or matches attacker-controlled patterns or changes the case of untrusted strings; we have not tested any exploit. We will update this when it can be confirmed, and remove this note.
The seven flaws
CVE identifiers had been requested but not yet assigned, so the advisory uses GitHub Security Advisory identifiers:
- GHSA-34m4-m9fh-gqp5: one-byte heap buffer overflow when changing the case of a crafted string. Known PoCs reach code execution in some scenarios.
- GHSA-87fm-7w84-j2px: integer overflow in case conversion leading to a heap buffer overflow. Known PoCs reach code execution in some scenarios.
- GHSA-7x2q-68qv-6p8x: double free when compiling a crafted regular expression. Known PoCs reach code execution in some scenarios.
- GHSA-3p8q-wmhx-vm2w: integer overflow in regular expression compilation leading to a heap buffer overflow. Known PoCs reach code execution in some scenarios.
- GHSA-7whj-cfh7-xgm4: heap buffer overflow in Regexp#to_s, which can disclose memory or run code. Known PoCs reach code execution in some scenarios.
- GHSA-wpqw-5qxg-m68r: out-of-bounds read in case-insensitive regular expression matching; PoCs show memory corruption under attacker control.
- GHSA-pvgc-g7gj-pv6h: out-of-bounds read in case-insensitive backreference matching, which can disclose memory or crash the process.
Affected and fixed versions
| Line | Affected | Fixed |
|---|---|---|
| 4.0 | 4.0.0 to 4.0.9 | 4.0.10 |
| 3.4 | 3.4.0 to 3.4.12 | 3.4.13 |
| 3.3 | 3.3.13 and earlier | 3.3.14 |
Ruby 3.3 is in its security maintenance phase. Ruby 3.2 and earlier have reached end of life and will not receive these fixes.
Who is exposed and what to do
The regular expression flaws matter most where an application compiles or matches patterns that users can supply, such as search features, filtering rules or admin tools that accept a regex. The case conversion flaws are broader, because changing the case of user input is common in web code. Teams running Rails or other Ruby applications should rebuild on the fixed release for their line, including base container images and any Ruby bundled in vendor appliances, and should plan a move off Ruby 3.2 or older, which now has known code execution bugs that will not be patched.
Sources
- Ruby: Security advisories, multiple vulnerabilities in Regexp and String case conversion, 18 November 2026
- Ruby 4.0.10 released, 18 November 2026
Categories & features
- Cybersecurity
- Application Security
- Web Security
TrustList Weekly
The week in software and IT, in one email
The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.
You may be interested in
FoxIO found seven of ten HTTP/3 stacks open to header amplification. quic-go, Cloudflare quiche, lsquic and Wireshark are fixed; Bun, the h3 crate and aioquic are not, and a proof of concept is public.
CVE-2026-114509 lets an attacker with no token log in as an existing user on apps using TokenGuard with MySQL or MariaDB. Upgrade to 13.29.0 or 12.68.0; a proof of concept is public.
Releases 26.12.1, 24.22.1 and 22.23.4 close ten CVEs, four rated High, and also drop trust in the compromised eMudhra intermediates through the bundled CA store.
PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 close CVE-2026-109618 and CVE-2026-109619. Every PHP install serving web requests is at risk, mod_php most of all, and PHP 8.1 and older get no official fix.
Two flaws rated Important hit all three supported lines, a third affects only Tomcat 11, and the fixed releases have been out since 12 October.
Google announced the removal a year ago; the XSLTEnabled enterprise policy and an origin trial keep it working only until Chrome 176, due on 17 August 2027.
Edge 159 disables the XSLTProcessor API and XSL stylesheet instructions by default. A temporary XSLTEnabled policy buys time until Edge 176 in summer 2027.
More on TrustList
Everything here links back to the same verified catalogue. Pick your next stop.
- More CybersecurityThe ranking for this subject
- CompaniesAgencies, consultancies and IT service providers, ranked by verified reviews.
- ProductsSoftware and SaaS with pricing, features, integrations and alternatives.
- AwardsAnnual recognition decided by verified reviews and an independent jury.
- LaunchesNew products and releases, voted up by the community every day.
- AI ModelsBenchmark scores and community ratings for every major model.
- RequestsBuyers describe what they need; vendors respond directly.
- PeopleReviewers, authors and makers with public profiles.
- ComparePut up to four listings side by side before you shortlist.