json Known Vulnerabilities & Fixes
json has 3 known security vulnerabilities in RubyGems (Ruby). Upgrade to version 2.19.2 or later to resolve all known issues. Data sourced from OSV, enriched with EPSS exploit probability and CISA KEV.
Low Immediate Risk
No actively exploited vulnerabilities detected. Monitor and update in your next maintenance window.
Recommended safe version: 2.19.2
Upgrading to 2.19.2 or later resolves all 3 known vulnerabilities in json. Run: gem install json -v 2.19.2
Is json in your project?
Check if you're affected and upgrade to 2.19.2 to stay secure.
Security Summary
- 5 affected version ranges have been identified across these 3 advisories.
- 100% of known issues have a published fixed version.
- Remediation: gem update json
Vulnerabilities
3 unique vulnerabilities — sorted by exploitation risk (KEV → EPSS → CVSS). Click a CVE/GHSA ID for full details. First disclosed Jul 27, 2020, most recently Mar 19, 2026 (2061 days apart).
| CVE / GHSA | Severity | Affected | Fixed In |
|---|---|---|---|
| CVE-2026-33210 Ruby JSON has a format string injection vulnerability | HIGH | 2.18.0, 2.18.1, 2.19.0, 2.19.1 (+8 more) | 2.19.2, 2.17.1.2, 2.15.2.1 |
| CVE-2025-27788 Out-of-bounds Read in Ruby JSON Parser | HIGH | 2.10.0, 2.10.1 | 2.10.2 |
| CVE-2020-10663 Unsafe object creation in json RubyGem | HIGH | 0.4.0, 0.4.1, 0.4.2, 0.4.3 (+64 more) | 2.3.0 |
About This Data
Vulnerability data for json is sourced from the Open Source Vulnerability (OSV) database, aggregating reports from GitHub Advisory Database, NIST NVD, and ecosystem-specific sources.
CVSS (Common Vulnerability Scoring System) scores reflect exploitability and impact. EPSS (Exploit Prediction Scoring System) scores indicate the probability of exploitation within the next 30 days. Vulnerabilities marked with are listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.
Related RubyGems (Ruby) Packages
Other packages in this ecosystem, ranked by shared vulnerabilities where available.
Check Your Dependencies
Scan your project to check if you're using a vulnerable version of json.