CyberSIXT reportingUpdated
Ruby vulnerabilities: seven memory flaws fixed, RCE PoCs exist
Part of the CVE-2026-132825 story · since 19 Nov
- Thu 19 Nov, 08:24 UTC. cybersixt, first report. Ruby vulnerabilities: seven memory flaws fixed, RCE PoCs exist. This article, 1st of 1.
Updated 19 November, 08:54 UTC. Corrected: one of the seven flaws has a CVE ID, CVE-2026-132825, which MITRE published at 06:34 UTC on Thursday; this article first said none had one.
Ruby has released versions 4.0.10, 3.4.13 and 3.3.14 to fix seven vulnerabilities in its regular expression engine and in the case conversion of strings, the project said in an advisory published at 00:00 UTC on Thursday. “We are aware of PoCs that prove some of them can be used to trigger remote code execution,” it said, and it strongly recommends upgrading.
One of the seven has a CVE ID so far. MITRE published CVE-2026-132825 at 06:34 UTC on Thursday for the one-byte overflow in case conversion. Ruby's advisory still says identifiers “have been requested” but “have not been assigned yet”, and lists the bugs only by their GitHub Security Advisory (GHSA) identifiers. They are the second set of fixes in Ruby's regular expression engine in four weeks: in October, Ruby patched three bugs that GitLab had found could be used for remote code execution on its servers, and one of the GitLab CVEs behind them is on the exploited-flaws list of the US Cybersecurity and Infrastructure Security Agency (CISA).
The seven flaws
Ruby's repository advisories rate three of the flaws critical, three high and one medium. They give no CVSS scores.
- GHSA-34m4-m9fh-gqp5 (critical): a one-byte heap buffer overflow when changing the case of a string in some single-byte encodings, such as ISO-8859-1 and Windows-1252. It is now CVE-2026-132825.
- GHSA-87fm-7w84-j2px (high): an integer overflow when changing the case of a string whose converted result exceeds 4 GiB, which causes a heap buffer overflow.
- GHSA-7x2q-68qv-6p8x (critical): a double free when Ruby parses a character class intersection (
&&) in a pattern. - GHSA-3p8q-wmhx-vm2w (critical): an overflow in the size of a compiled pattern that lets Ruby write past the end of a heap buffer.
- GHSA-7whj-cfh7-xgm4 (high): a heap buffer overflow in
Regexp#to_s. - GHSA-wpqw-5qxg-m68r (high): an out-of-bounds read in case-insensitive matching, which Ruby says PoCs show “can lead to memory corruption in an attacker-controlled way”.
- GHSA-pvgc-g7gj-pv6h (medium): an out-of-bounds read in case-insensitive backreference matching that may disclose memory contents or crash the process.
Ruby says it knows of PoCs that trigger remote code execution “in some scenarios” for five of them: the three critical flaws, the 4 GiB case-conversion overflow and the Regexp#to_s overflow. Stephan Lipp of Ada Logics, together with Anthropic, reported four of the flaws, according to the advisory. HackerOne researchers baba__yaga and aphantom reported one each, and Hiroya Fujinami and Hiroshi SHIBATA the last.
Who is exposed
Four of the five Regexp advisories describe the risk in applications that compile or use patterns built from attacker-controlled strings; the backreference read is reached by matching a crafted string. The October advisory spells out what that means: passing such a string to Regexp.new, Regexp.union or Regexp.compile, or interpolating it into a literal such as /#{input}/. Applications that only use patterns written by their own developers were not affected by those bugs, and Ruby said Regexp.timeout does not protect against them.
The two String flaws carry no such condition. Ruby says “changing the case of a crafted string may allow remote code execution”, and the advisories name no workaround for any of the seven other than upgrading.
The October fixes behind GitLab's CVEs
GitLab compiles patterns its users supply, such as those in CI configuration, with Regexp.new, Ruby explained on 23 October. GitLab found that crafted patterns could corrupt memory and patched the Ruby it ships, assigning CVE-2026-89078, CVE-2026-93577, CVE-2026-97229 and CVE-2026-110264. CISA added CVE-2026-97229 to its Known Exploited Vulnerabilities catalogue on 29 October. Its entry describes unauthenticated code execution through a crafted regular expression in a CI/CD configuration, links GitLab's 19.4.2 patch release and notes that other products “can potentially be affected by the same underlying Ruby/Onigmo” issue.
On Tuesday, Ruby changed how it classifies such bugs. It had generally considered compiling a pattern from untrusted input unsafe and had not requested CVEs for the October fixes. It has now decided “that memory corruption reachable by compiling an untrusted pattern is a vulnerability in Ruby”, it said, and published three critical advisories for them. The seven new advisories followed two days later.
One CVE ID so far: CVE-2026-132825
The CVE record lists MITRE as the organisation that assigned it and does not say who requested it. It cites Ruby's advisory and GHSA-34m4-m9fh-gqp5, and gives the same affected versions.
The record and Ruby rate the flaw differently. MITRE's record scores it 7.4 (high) under CVSS 3.1, with a local attack vector and high attack complexity. Ruby's repository advisory rates it critical and says PoCs show it “can be used to trigger RCE in some scenarios”. At 08:54 UTC on Thursday that advisory still said “a CVE ID has been requested and is pending”, and none of the other six flaws had a CVE ID on its advisory.
For the October bugs, Ruby asks anyone tracking them, “for example in a security scanner”, to use its advisories or GitLab's CVE identifiers until its own are assigned. When CyberSIXT checked at 08:18 UTC on Thursday, none of the ten GHSA identifiers had an entry in GitHub's global Advisory Database; they appear only on the ruby/ruby security page.
Affected versions and fix
The advisory lists Ruby 3.3.13 and earlier, 3.4.0 through 3.4.12 and 4.0.0 through 4.0.9 as affected. The fixes are in Ruby 4.0.10, 3.4.13 and 3.3.14. Ruby 3.2 and earlier have reached end of life and will not receive them.
None of Ruby's ten advisories names a CVE ID of its own yet.
How the story developed
1 article from 1 outlet since 19 Nov. Still developing; the latest report was 9 hours ago. This was the first report.
- Thu 19 Nov, 08:24 UTC. cybersixt, first report. Ruby vulnerabilities: seven memory flaws fixed, RCE PoCs exist. This article, 1st of 1.
- CVE not in KEV
- No CVE
- Larger: an outlet’s first report
- Coverage over time
Show all 1 articles as a listHide the list
- Thu 19 NovDay 01
- Ruby vulnerabilities: seven memory flaws fixed, RCE PoCs exist08:24 · cybersixt · First report · This article, 1st of 1
Sources
- Ruby advisory: multiple vulnerabilities in Regexp and StringPrimary sourceruby-lang.org
- CVE-2026-132825 recordPrimary sourcecve.org
- Ruby advisory GHSA-34m4-m9fh-gqp5Primary sourcegithub.com
- Ruby advisory GHSA-87fm-7w84-j2pxPrimary sourcegithub.com
- Ruby advisory GHSA-7x2q-68qv-6p8xPrimary sourcegithub.com
- Ruby advisory GHSA-3p8q-wmhx-vm2wPrimary sourcegithub.com
- Ruby advisory GHSA-7whj-cfh7-xgm4Primary sourcegithub.com
- Ruby advisory GHSA-wpqw-5qxg-m68rPrimary sourcegithub.com
More reporting
- VMware vCenter zero-day CVE-2026-123890 exploited in September19 Nov
- Revolut data breach: Dutch police foil violence on customers19 Nov
- N-able breach knocks Mail Assure and SpamExperts portals offline19 Nov
- European Commission cyberattack tied to AI hacking tool ARTEX19 Nov
- SBC Medical data breach hits 1.6M Shonan Beauty Clinic customers19 Nov
Written by CyberSIXT from the sources above.How we reportCorrectionsRSS