CVERadar
HIGH · CVSS 3.1 7.4Public PoCEPSS 1.98% (p81)Threat level 42

CVE-2026-132825: CVE-2026-132825: Ruby before 3.3.14, 3.4.13, and 4.0.10 has a heap-based buffer overflow during case conver…

Unknown · Ruby · NVD published 2026-11-19 · posted 2026-11-20 · last modified 2026-11-20

CVE-2026-132825 at a glance

CVE-2026-132825 is a high-severity Buffer Overflow vulnerability in Ruby, with a CVSS 3.1 base score of 7.4. NVD published it on 2026-11-19 and classifies the weakness as CWE-122. Public exploit code: 6 public GitHub proof-of-concept repositories from 6 accounts, with the earliest exploit evidence dated 2026-11-19. FIRST EPSS puts the probability of exploitation activity in the next 30 days at 1.98% (percentile 80.9, scored 2026-11-21). NVD does not list a fixed version, so the vendor advisory is the reference for the fix. CVERadar maps 1 MITRE ATT&CK technique across Execution, inferred from the CWE and the description. Its CVERadar threat level is 42/100.

What it is

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.

WeaknessCWE-122 definition
CVSS vectorCVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H (source: MITRE)
ATT&CK tacticsExecution

Exploitation evidence

First exploit evidence seen: 2026-11-19 (earliest date across the sources below).

Exploited in the wild

No source on this site lists in-the-wild exploitation yet (CISA KEV, VulnCheck KEV).

Public exploit code

GitHub proof-of-concept repositories

6 public repositories from 6 accounts, first seen 2026-11-19. Most starred: scadastrangelove/ruby2shell (0 stars), view the scadastrangelove/ruby2shell repository on GitHub.

Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.

Sources: nomi-sec/PoC-in-GitHub.

Patches, mitigations and detection

Fixed versions

NVD does not list a fixed version for this CVE. Use the vendor advisory below.

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

No vendor-tagged reference yet; see the full reference list.

MITRE ATT&CK mitigations for this chain

  • M1050 Exploit Protection (for T1203) : Security applications that look for behavior used during exploitation such as Windows Defender Exploit Guard (WDEG) and the Enhanced Mitigation Experience Toolkit (EMET) can be used to mitigate some exploitation behavior. Control flow integrity checking is another way to potentially identify and stop a software exploi
  • M1051 Update Software (for T1203) : Perform regular software updates to mitigate exploitation risk. Keeping software up-to-date with the latest security patches helps prevent adversaries from exploiting known vulnerabilities in client software, reducing the risk of successful attacks.
  • M1048 Application Isolation and Sandboxing (for T1203) : Browser sandboxes can be used to mitigate some of the impact of exploitation, but sandbox escapes may still exist. Other types of virtualization and application microsegmentation may also mitigate the impact of client-side exploitation. Risks of additional exploits and weaknesses in those systems may still exist.

Detection Generic guidance

  • Execution: Watch for the service process spawning shells or script interpreters (cmd.exe, powershell, sh, bash, python) via EDR process-tree rules.

Response checklist Generic guidance

  1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
  2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
  3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
  4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.

Patching closes the hole, but someone still has to watch the endpoints; managed endpoint protection from LayerLogix covers EDR and MDR.

Sources