CVE-2026-132825
validatedZero produced an exploit or a check.GHSA-8452-w857-wpmw ↗EUVD-2026-129481 ↗
description
Ruby releases addressed by the November 2026 coordinated update contain multiple memory-safety flaws in regular-expression processing and string case conversion. An attacker may cause memory corruption, and potentially code execution, when an application processes attacker-controlled regular expressions or strings through the affected operations.
mitigation
Update Ruby to the vendor-remediated release for your supported release line; the exact fixed versions are not present in the supplied evidence. Until updates are deployed, restrict untrusted input from reaching regular-expression compilation and affected string-conversion paths.
fixed in 3.3.14, 3.4.13, 4.0.10
outcome
Contextual check: a technique exists and was validated, but no deterministic check could cover this one.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-11-19 06:34Zcve.org record for CVE-2026-132825
- 2026-11-19 08:42Zthehackernews: trigger signal, started the run
- 2026-11-19 08:42ZRuby Ships Fixes for 7 Flaws, Including Critical Ruby2Shell, Said to Hit Default Rails Apps Pre-Auth
- 2026-11-20 10:45Zevenomn/CVE-2026-132825
this entry in the feed
GET /api/v1/feed/CVE-2026-132825
{ "etk_id": "ETK-2026-4904", "cve_id": "CVE-2026-132825", "display_id": "CVE-2026-132825", "ghsa_id": "GHSA-8452-w857-wpmw", "euvd_id": "EUVD-2026-129481", "status": "published", "anchor_state": "anchored", "title": "Memory-safety flaws in Ruby Regexp and string handling", "summary": "Ruby releases addressed by the November 2026 coordinated update contain multiple memory-safety flaws in regular-expression processing and string case conversion. An attacker may cause memory corruption, and potentially code execution, when an application processes attacker-controlled regular expressions or strings through the affected operations.", "mitigation": "Update Ruby to the vendor-remediated release for your supported release line; the exact fixed versions are not present in the supplied evidence. Until updates are deployed, restrict untrusted input from reaching regular-expression compilation and affected string-conversion paths.", "vendor": "Ruby", "product": "Ruby", "affected": [ { "affected_notes": [], "affected_ranges": [ "<= 3.3.13" ], "ecosystem": null, "fixed_versions": [ "3.3.14" ], "package_name": "ruby", "purl": null }, { "affected_notes": [], "affected_ranges": [ ">= 3.4.0, <= 3.4.12" ], "ecosystem": null, "fixed_versions": [ "3.4.13" ], "package_name": "ruby", "purl": null }, { "affected_notes": [], "affected_ranges": [ ">= 4.0.0, <= 4.0.9" ], "ecosystem": null, "fixed_versions": [ "4.0.10" ], "package_name": "ruby", "purl": null } ], "cwes": [ 122 ], "cvss_score": 7.4, "cvss_src": "nvd", "cvss_vector": "CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H", "epss_score": null, "epss_percentile": null, "epss_asof": null, "automation": "contextual", "check": true, "check_confidence_basis": "assessed", "exploit": false, "pipeline_minutes": 33.9180608, "t0_at": "2026-11-19T06:34:26.335000+00:00", "signals": { "check": { "at": "2026-11-19T09:19:20.663754+00:00", "days": 0.11451769391203703, "is_lower_bound": false, "measured_at": "2026-11-19T06:34:26.335000+00:00", "url": null }, "public_poc": { "at": "2026-11-20T00:25:42+00:00", "days": 0.7439313078703703, "is_lower_bound": false, "measured_at": "2026-11-19T06:34:26.335000+00:00", "url": "https://github.com/evenomn/CVE-2026-132825" }, "trigger_signal": { "at": "2026-11-19T08:42:11+00:00", "days": 0.08871140046296297, "is_lower_bound": false, "measured_at": "2026-11-19T06:34:26.335000+00:00", "url": "https://thehackernews.com/2026/11/ruby-releases-fixes-for-7-regex-and.html" } } }
Anchor corroborated by the cve.org commit 829986ff4448.
published 2026-11-19 08:45Z
last change 2026-11-20 11:18Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.