# Ruby string case conversion can corrupt memory (CVE-2026-132825)

Canonical: https://www.oktsec.com/radar/ruby-string-case-conversion-cve-2026-132825
Publisher: Oktsec
Language: en
Published: 2026-11-20T13:10:14Z
Updated: 2026-11-20T13:10:14Z
Record reviewed: 2026-11-20T13:10:14Z
Latest evidence check: 2026-11-20T13:10:14Z
Disclosed: 2026-11-19

Applications that convert the case of untrusted strings in certain encodings can corrupt process memory. The Ruby project reports a code execution demonstration for this flaw.

## Evidence and response priority

- Category: Vulnerability
- Oktsec priority: Act now
- Rationale: The demonstration applies to an operation that can process external input. Prioritize applications that change the case of strings in affected encodings.
- Evidence: Attacks not established
- Verification: Vendor confirmed
- Fix status: Fix available
- Exposure requirement: Application or configuration dependent
- Vendor: Ruby
- Products: Ruby
- CVEs: CVE-2026-132825

## Technical overview

CVE-2026-132825 concerns case conversion in encodings such as ISO-8859-1 and Windows-1252. The affected component is the interpreter. Updating an application dependency alone leaves the deployed Ruby runtime unchanged.

## Recommended response

Update the Ruby runtime to 3.3.14, 3.4.13 or 4.0.10 on the matching branch. Rebuild deployed images and restart workers using the old interpreter.

Relevant to: Teams operating Ruby web applications and import workers.

## CVE attribution

- CVE-2026-132825: Ruby — Ruby; CVSS 3.1: 7.4. [Source](https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/132xxx/CVE-2026-132825.json)

## Exploit demonstration

Status: Exploit demonstrated
CVEs: CVE-2026-132825
Checked: 2026-11-20T13:10:14Z

Ruby maintainers report a proof of concept demonstrating code execution under specific conditions for this case conversion flaw.

[Supporting source](https://github.com/ruby/ruby/security/advisories/GHSA-34m4-m9fh-gqp5)

## Affected systems and fixes

### Ruby

Affected: 3.3 through 3.3.13, 3.4.0 through 3.4.12, and 4.0.0 through 4.0.9.

Fixed release / action: 3.3.14; 3.4.13; 4.0.10; Move unsupported runtimes to a maintained branch.

Confirm the running version against the vendor advisory, including any distribution backports.

## CISA KEV evidence

Catalog: 2026.11.20
Checked: 2026-11-21T21:27:34.352Z

No matching CVE appears in the reviewed catalog snapshot.

CISA KEV inclusion establishes known exploitation of the listed CVE, not compromise of your environment. Absence does not rule out exploitation. The date added is not the first attack date. Federal deadlines and forensic triage requirements are context, not universal obligations for private organizations or businesses in Latin America.

## Supporting evidence

Snapshot checked: 2026-11-22T13:41:03.396Z. These dates do not change the incident’s editorial review date.

### FIRST EPSS forecast

- [CVE-2026-132825](https://api.first.org/data/v1/epss?cve=CVE-2026-132825): 1.98% probability of observed exploitation in the next 30 days; percentile 81%; score date 2026-11-21.

EPSS is a prediction, not exploitation evidence or organization-specific risk. Confirmed exploitation takes precedence. A missing score is not zero. Check status: available; last successful check: 2026-11-22T13:41:03.396Z.

### Official regional advisories

- [Vulnerabilidad en Ruby](https://www.cert.gov.py/vulnerabilidad-en-ruby/) — CERT-PY, Paraguay; publication 2026-11-20T11:53:16.000Z; observed 2026-11-22T13:41:03.396Z; matched by exact CVE identifier.

Publisher country does not establish victim location. Original notices may repeat the same underlying advisory.

## Response checklist

1. **Find Ruby processes that handle external text** — Include background workers that import files or normalize text from external systems.
2. **Replace vulnerable runtimes** — Check the package or image used by the deployed process, update the corresponding branch and restart the service.
3. **Verify the runtime after deployment** — Check the Ruby version used by each web and background worker.

## Relevance to AI environments

Include Ruby tools that normalize text received from agents or external feeds.

## Sources

- [Ruby security advisory for case conversion](https://github.com/ruby/ruby/security/advisories/GHSA-34m4-m9fh-gqp5) — Ruby; Vendor notice; checked 2026-11-20T13:10:14Z
- [CVE-2026-132825 CVE record](https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/132xxx/CVE-2026-132825.json) — mitre; Research report; checked 2026-11-20T13:10:14Z

## Editorial record

- 2026-11-20T13:10:14Z: Published the affected configurations, branch fixes and steps to verify the update.

## Use this advisory in Radar

Use the Advisory view to understand the issue and its evidence, Affected systems to compare versions, and Response plan to record applicability, an owner and action progress. Plans are saved only in the current browser and can be downloaded for sharing; they are not a shared team account or an automated scan. Completing a plan does not validate remediation. Talk to Oktsec opens a technical consultation with the advisory and selected service preserved. Scope, fees and access are agreed before any assessment.

[Open advisory](https://www.oktsec.com/radar/ruby-string-case-conversion-cve-2026-132825) · [Build a response plan](https://www.oktsec.com/radar/ruby-string-case-conversion-cve-2026-132825#review-workspace)

- [Exposure check consultation](https://www.oktsec.com/contact?source=radar&intent=assessment&item=ruby-string-case-conversion-cve-2026-132825&service=exposure_check)
- [Patch verification consultation](https://www.oktsec.com/contact?source=radar&intent=assessment&item=ruby-string-case-conversion-cve-2026-132825&service=patch_verification)

## Scope and corrections

Radar is a selected editorial collection, not a complete vulnerability database or a scan of your environment. Priorities are Oktsec analysis. Source confirmation and checklist completion do not establish whether your systems are compromised or secure.

[Sources and methodology](https://www.oktsec.com/radar/about). Report corrections with supporting sources to info@oktsec.com. Do not send secrets or private incident data.

