CVE-2026-33210: CWE-134: Use of Externally-Controlled Format String in ruby json
Ruby JSON is a JSON implementation for Ruby. From version 2.14.0 to before versions 2.15.2.1, 2.17.1.2, and 2.19.2, a format string injection vulnerability can lead to denial of service attacks or information disclosure, when the allow_duplicate_key: false parsing option is used to parse user supplied documents. This issue has been patched in versions 2.15.2.1, 2.17.1.2, and 2.19.2.
AI Analysis
Technical Summary
CVE-2026-33210 is a vulnerability in the Ruby JSON library, specifically in versions 2.14.0 through versions prior to 2.15.2.1, 2.17.1.2, and 2.19.2. The issue arises from improper handling of externally-controlled format strings when the allow_duplicate_key: false parsing option is enabled. This option is intended to prevent duplicate keys in JSON objects but introduces a format string injection risk due to unsafe string formatting operations internally. An attacker can craft malicious JSON input that triggers this vulnerability, potentially causing denial of service by crashing the parser or leaking sensitive information through unintended format string processing. The vulnerability does not require authentication or user interaction, and the attack vector is network-based, as it involves parsing attacker-controlled JSON data. The CVSS 4.0 vector indicates low attack complexity, no privileges required, and no user interaction needed, with high impact on availability and moderate impact on confidentiality. The vulnerability has been patched in Ruby JSON versions 2.15.2.1, 2.17.1.2, and 2.19.2. No public exploits are known at this time, but the severity and ease of exploitation make timely patching critical.
Potential Impact
This vulnerability can significantly impact organizations that rely on Ruby JSON for parsing untrusted JSON data, especially when the allow_duplicate_key: false option is used. Successful exploitation can lead to denial of service, disrupting application availability and potentially causing downtime or degraded service. Information disclosure risks may expose sensitive data, undermining confidentiality. Since Ruby is widely used in web applications, APIs, and backend services, exploitation could affect a broad range of industries including finance, healthcare, e-commerce, and technology. The lack of authentication requirements and ease of exploitation increase the threat surface, enabling remote attackers to launch attacks without prior access. Organizations that do not promptly update their Ruby JSON libraries risk operational disruption and data breaches, which could lead to financial loss, reputational damage, and regulatory penalties.
Mitigation Recommendations
Organizations should immediately identify all systems using the Ruby JSON library versions 2.14.0 up to but not including 2.15.2.1, 2.17.1.2, and 2.19.2, especially those utilizing the allow_duplicate_key: false parsing option. The primary mitigation is to upgrade to the patched Ruby JSON versions 2.15.2.1, 2.17.1.2, or 2.19.2 as appropriate. If immediate upgrading is not feasible, consider disabling the allow_duplicate_key: false option temporarily to avoid triggering the vulnerability, though this may reduce JSON parsing strictness. Implement input validation and sanitization to limit exposure to malicious JSON inputs. Employ runtime application self-protection (RASP) or web application firewalls (WAFs) with custom rules to detect and block suspicious JSON payloads. Monitor application logs for crashes or unusual behavior indicative of exploitation attempts. Conduct security testing and code reviews focusing on JSON parsing components. Finally, maintain an inventory of Ruby dependencies and establish a patch management process to rapidly respond to future vulnerabilities.
Affected Countries
United States, United Kingdom, Germany, Japan, Canada, Australia, France, India, Netherlands, South Korea, Brazil, Singapore
CVE-2026-33210: CWE-134: Use of Externally-Controlled Format String in ruby json
Description
Ruby JSON is a JSON implementation for Ruby. From version 2.14.0 to before versions 2.15.2.1, 2.17.1.2, and 2.19.2, a format string injection vulnerability can lead to denial of service attacks or information disclosure, when the allow_duplicate_key: false parsing option is used to parse user supplied documents. This issue has been patched in versions 2.15.2.1, 2.17.1.2, and 2.19.2.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-33210 is a vulnerability in the Ruby JSON library, specifically in versions 2.14.0 through versions prior to 2.15.2.1, 2.17.1.2, and 2.19.2. The issue arises from improper handling of externally-controlled format strings when the allow_duplicate_key: false parsing option is enabled. This option is intended to prevent duplicate keys in JSON objects but introduces a format string injection risk due to unsafe string formatting operations internally. An attacker can craft malicious JSON input that triggers this vulnerability, potentially causing denial of service by crashing the parser or leaking sensitive information through unintended format string processing. The vulnerability does not require authentication or user interaction, and the attack vector is network-based, as it involves parsing attacker-controlled JSON data. The CVSS 4.0 vector indicates low attack complexity, no privileges required, and no user interaction needed, with high impact on availability and moderate impact on confidentiality. The vulnerability has been patched in Ruby JSON versions 2.15.2.1, 2.17.1.2, and 2.19.2. No public exploits are known at this time, but the severity and ease of exploitation make timely patching critical.
Potential Impact
This vulnerability can significantly impact organizations that rely on Ruby JSON for parsing untrusted JSON data, especially when the allow_duplicate_key: false option is used. Successful exploitation can lead to denial of service, disrupting application availability and potentially causing downtime or degraded service. Information disclosure risks may expose sensitive data, undermining confidentiality. Since Ruby is widely used in web applications, APIs, and backend services, exploitation could affect a broad range of industries including finance, healthcare, e-commerce, and technology. The lack of authentication requirements and ease of exploitation increase the threat surface, enabling remote attackers to launch attacks without prior access. Organizations that do not promptly update their Ruby JSON libraries risk operational disruption and data breaches, which could lead to financial loss, reputational damage, and regulatory penalties.
Mitigation Recommendations
Organizations should immediately identify all systems using the Ruby JSON library versions 2.14.0 up to but not including 2.15.2.1, 2.17.1.2, and 2.19.2, especially those utilizing the allow_duplicate_key: false parsing option. The primary mitigation is to upgrade to the patched Ruby JSON versions 2.15.2.1, 2.17.1.2, or 2.19.2 as appropriate. If immediate upgrading is not feasible, consider disabling the allow_duplicate_key: false option temporarily to avoid triggering the vulnerability, though this may reduce JSON parsing strictness. Implement input validation and sanitization to limit exposure to malicious JSON inputs. Employ runtime application self-protection (RASP) or web application firewalls (WAFs) with custom rules to detect and block suspicious JSON payloads. Monitor application logs for crashes or unusual behavior indicative of exploitation attempts. Conduct security testing and code reviews focusing on JSON parsing components. Finally, maintain an inventory of Ruby dependencies and establish a patch management process to rapidly respond to future vulnerabilities.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-17T23:23:58.313Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 69bdd4681188d0bb0cbbf670
Added to database: 3/20/2026, 11:12:40 PM
Last enriched: 3/28/2026, 9:27:35 PM
Last updated: 5/5/2026, 1:06:07 AM
Views: 86
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.