Skip to content

High 7.4Patch available

CVE-2026-132825

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.

How scary is it?

updated 21 Nov 2026
  • Yes

    Works without logging in1

    No account and no user action needed (CVSS PR:N, UI:N).

  • No

    Reachable over the network1

    Needs local access to the machine, such as a shell or a logged-in user (CVSS AV:L).

  • Yes

    Proof-of-concept code is public2

    6 GitHub proofs of concept. GitHub proofs of concept are unvetted: some are fake or carry malware. No Exploit-DB entry or Metasploit exploit module on record.

  • None known

    Attacks seen in the wild1

    None reported that we know of. CISA's SSVC assessment says exploitation: none.

  • No

    On CISA's exploited list3

    Not in the catalog as of our last sync.

Scare-o-meter

Routine patch

Serious on paper, with no sign of attacks that we know of. Patch in your normal cycle.

  1. Low signal
  2. Routine patch
  3. Act this week
  4. Drop everything

Why: our alert rule found no exploitation evidence and no easy remote attack path in the data we hold. Read from the same rule that decides our alert emails.

Are you affected? only if all are true

  1. You run ruby-lang Ruby in an affected version< 3.3.14 / >= 3.4.0 and < 3.4.13 / >= 4.0.0 and < 4.0.10

    The CVE record states no fixed release.

    As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.

    See the affected products table · Source 1

  2. The attacker already has local access to the machine

    CVSS attack vector: Local (AV:L). Local access required, such as a shell or a logged-in user.

    Source 1

  3. Specific conditions are met that the attacker does not control

    CVSS attack complexity: High (AC:H). Needs specific conditions, a race or a particular configuration. The CVE record does not always say which.

    Source 1

Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.

What to do

  1. Per our analysisA patch is available

    The CVE record we hold states no fixed release number. See the advisories in the references.

    See the references

CVSS
7.4Highscored by the publisher (CNA)
Exploited in the wild
Not knownUnvetted proof-of-concept code on GitHub; not in CISA KEV
EPSS
2.0%chance of exploitation in the next 30 daystop 20% of scored CVEsFIRST score of 21 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
19 Nov 2026analysed here 21 Nov 2026

Summary

Triage

Attack surface
Server-side
Exploitable
At runtime
Attack vector
local
Weakness
Can a WAF block it?
Partly. See why

Executive summary (AI-written)

CVE-2026-132825 is a vulnerability identified in Ruby versions prior to 3.3.14, 3.4.13, and 4.0.10, which poses a moderate risk with a CVSS score of 7.4. This vulnerability allows for a heap-based buffer overflow during case conversion processes, potentially enabling attackers to write outside designated memory buffers. Although specific systems affected have not been detailed, the implications affect a wide range of applications that leverage Ruby, including various desktop and server environments. The absence of a patch heightens the urgency for organizations to assess their Ruby deployments and implement protective measures. With no immediate patch available, companies are advised to understand the potential risks this vulnerability introduces, particularly in production environments. Affected organizations should prioritize vulnerability assessments and consider implementing mitigations to reduce exposure to attacks that exploit this buffer overflow, ensuring that inappropriate access to sensitive data does not occur. Proactively addressing this vulnerability will strengthen the organization's security posture and protect against potential exploitation.

Technical analysis (AI-written)

CVE-2026-132825 indicates a heap-based buffer overflow that occurs in Ruby due to improper handling of case conversion for certain character sets such as ISO-8859-1 and Windows-1252. This type of vulnerability could allow an attacker to overwrite memory outside of intended bounds, which can lead to arbitrary code execution or data corruption, depending on the nature of the attack vector. The CVSS score of 7.4 indicates a high potential for exploitation, particularly in systems that utilize Ruby for web applications, APIs, or any form of data processing involving untrusted input, such as user-provided strings. Exploitation of this vulnerability could occur if an attacker crafts input data that triggers the buffer overflow during case handling operations. Such scenarios are common in applications where user input is processed directly without proper sanitization. Given the prevalence of Ruby in web development, this could potentially impact many server instances running Ruby on Rails or any Ruby-based applications that perform string manipulations. One critical aspect to highlight is the lack of a patch at this time, which means mitigation strategies must be adopted immediately to safeguard systems from potential exploitation. Organizations should start by reviewing their application codebases to identify uses of Ruby string operations, especially those involving case conversion. Employing input validation and sanitization measures will help in mitigating the risks posed by this vulnerability. Another preventive measure includes restricting user input size and type to ensure that any malicious attempts to exploit the buffer overflow are less likely to succeed. Longer-term, it is essential for development and security teams to stay updated with Ruby’s upcoming releases and patches. Monitoring Ruby’s official repository and security bulletins will provide crucial information on fixes as they become available. Additionally, organizations should plan regular updates to their Ruby installations and implement a robust monitoring strategy to detect any anomalous application behavior that might indicate exploitation attempts. As with any significant vulnerability, thorough testing and code reviews should be initiated once patches are released to ensure all associated risks are adequately addressed.

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources.

Affected products

ProductAffected versions
ruby-lang Ruby< 3.3.14>= 3.4.0 and < 3.4.13>= 4.0.0 and < 4.0.10Vendor says fixed in: not stated

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Fix and mitigation

WAF and other mitigations

Can a WAF block it? Partly. AWS WAF and Cloudflare publish WAF rules written for this CVE. Such rules block the known exploit requests and buy time, but attackers can change the request to get past them, so they do not replace the patch.

Also consider: patch · enable the vendor rule in block mode

Based on WAF vendor rules published for this CVE. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Not listed as of our last sync.
Public exploit code
Unvetted proof-of-concept code on GitHub: 6 GitHub proofs of concept
CISA SSVC
exploitation none, automatable no, technical impact totalAssessed by CISA 19 Nov 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

GitHub proofs of concept

and 2 more repositories

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 19 Nov 2026First proof-of-concept repository on GitHub (unvetted)
  2. 19 Nov 2026Publishedsame day later
  3. 19 Nov 2026CISA SSVC assessment: exploitation nonesame day later
  4. 21 Nov 2026CVE record last updated1 day later
  5. 21 Nov 2026Analysed by vulneraibility.comsame day later

CVSS vector

CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

MetricValueWhat it means
Attack vectorLocalLocal access required (shell, logged-in user).
Attack complexityHighNeeds specific conditions, a race or a particular configuration.
Privileges requiredNoneThe attacker needs no prior access.
User interactionNoneNo victim action needed.
ScopeUnchangedImpact stays within the vulnerable component.
ConfidentialityHighTotal data disclosure possible.
IntegrityHighComplete modification possible.
AvailabilityHighFull outage possible.

Common questions

Is CVE-2026-132825 being exploited?

Not confirmed. CVE-2026-132825 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 2.0% probability of exploitation in the next 30 days.

How severe is CVE-2026-132825?

CVE-2026-132825 is rated High with a CVSS score of 7.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-132825?

Yes. A fix has been recorded for CVE-2026-132825. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

12 references in the CVE record, grouped by the tags the record gives them.

Other links (12)

Show 6 more

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.