cve.bz

CVE-2026-132825 (Ruby2Shell) ruby-lang ruby: Heap-based Buffer Overflow

7.4 highEPSS 2.0%

Known as Ruby2Shell

High (7.4) in ruby-lang ruby. EPSS 2.0% estimated probability of exploitation activity in the next 30 days.

On this page
Ruby before 3.3.14, 3.4.13, and 4.0.10 has a heap-based buffer overflow during case conversion. One byte can be written outside a buffer for, for example, ISO-8859-1 or Windows-1252.

Severity

CVSS 3.1

7.4 high
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
2.0% estimated probability of exploitation activity in the next 30 days; 81st percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-19. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-122 Heap-based Buffer Overflow
Published
Modified
Assigned by
mitre (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-132825 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-132825?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-132825?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-132825 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
ruby-lang Rubybefore 3.3.14
ruby-lang Rubyfrom 3.4.0 before 3.4.13
ruby-lang Rubyfrom 4.0.0 before 4.0.10

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12ruby3.13.1.7-1~deb12u2DEBIAN-CVE-2026-132825 DLA-4926-1
Debian13ruby3.33.3.14-0+deb13u1DEBIAN-CVE-2026-132825 DSA-6644-1
Debian14ruby3.3no fix listedDEBIAN-CVE-2026-132825
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 1 morejrubyno fix listedUBUNTU-CVE-2026-132825
Ubuntu22.04:LTSruby3.0no fix listedUBUNTU-CVE-2026-132825
Ubuntu24.04:LTSjruby, ruby3.2no fix listedUBUNTU-CVE-2026-132825
Ubuntu26.04:LTS, 26.10jruby, ruby3.3no fix listedUBUNTU-CVE-2026-132825
UbuntuPro:16.04:LTSruby2.3no fix listedUBUNTU-CVE-2026-132825
UbuntuPro:18.04:LTSruby2.5no fix listedUBUNTU-CVE-2026-132825
UbuntuPro:20.04:LTSruby2.7no fix listedUBUNTU-CVE-2026-132825
Azure Linux3fluent-bitno fix listedAZL-115796
Azure Linux3rubyno fix listedAZL-114635
Alpaquita23, streamrubyno fix listedBELL-CVE-2026-132825
Alpaquita25ruby3.4.13-r0BELL-CVE-2026-132825

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.

Red Hat

Red Hat rates this Critical.

Red Hat's statement

This vulnerability is rated as Critical severity because successful exploitation can result in memory corruption or arbitrary code execution within the context of the running Ruby process. While heap memory corruption carries significant integrity and availability risks, successful attacks depend on complex memory layout manipulation and the application converting strings under specific non-UTF-8 character encodings. Most standard deployments process UTF-8 encoded text by default, which restricts exposure under typical configurations.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat 3scale API Management Platform 23scale-amp2/backend-rhel8Affected
Red Hat 3scale API Management Platform 23scale-amp2/system-rhel8Not affected
Red Hat 3scale API Management Platform 23scale-amp2/system-rhel9Affected
Red Hat 3scale API Management Platform 23scale-amp2/zync-rhel9Affected
Red Hat Enterprise Linux 10pcsAffected
Red Hat Enterprise Linux 10rubyAffected
Red Hat Enterprise Linux 10ruby4.0Affected
Red Hat Enterprise Linux 6rubyOut of support scope
Red Hat Enterprise Linux 7pcsAffected
Red Hat Enterprise Linux 7rubyAffected
Red Hat Enterprise Linux 8pcsAffected
Red Hat Enterprise Linux 8ruby:2.5/rubyAffected
Red Hat Enterprise Linux 8ruby:3.3/rubyAffected
Red Hat Enterprise Linux 9pcsAffected
Red Hat Enterprise Linux 9rubyAffected
Red Hat Enterprise Linux 9ruby:3.3/rubyAffected
Red Hat Enterprise Linux 9ruby:4.0/rubyAffected
Red Hat Hardened Imagesruby3.3Affected
Red Hat Hardened Imagesruby3.4Affected
Red Hat Hardened Imagesruby4.0Affected
31 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-132825.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON