VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

json: vulnerability history, versions and safety

json is a package in the RubyGems ecosystem. Vulert records 6 vulnerabilities for it across 89 releases, from Oct 2017 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
6 vulnerabilities recorded H4 L2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 07 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all json vulnerabilities

Vulert verdict on json 3.1.0 i

Updated on 23 Oct 2026

Good news: 3.1.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 6.

Package health score 79/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

What to do: Stay on 3.1.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 3.1.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 3.1.0 — unaffected i
  • Vulnerabilities on record 6 over 8 years · 3 in the last year i
  • Latest disclosure 07 Aug 2026 i
  • Highest CVSS 8.3 i
  • With no published fix 0 i
  • Stars 784 i
  • Last release this month i
  • Licence Ruby i

Version list, release dates, licence and dependants published by RubyGems, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for json, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
3.1.0 13 Oct 2026 none Ruby — Details →
3.0.2 09 Sep 2026 none Ruby — Details →
3.0.1 08 Sep 2026 none Ruby — Details →
3.0.0 07 Sep 2026 none Ruby — Details →
3.0.0.rc1 11 Aug 2026 none Ruby — Details →
2.21.2 31 Jul 2026 none Ruby — Details →
2.21.1 13 Jul 2026 L1 Ruby Yes Details →
2.21.0 12 Jul 2026 L1 Ruby Yes Details →
2.20.0 23 Jun 2026 L1 Ruby Yes Details →
2.19.9 11 Jun 2026 none Ruby — Details →
2.19.8 03 Jun 2026 L1 Ruby Yes Details →
2.19.7 28 May 2026 L1 Ruby Yes Details →
2.19.6 28 May 2026 L1 Ruby Yes Details →
2.19.5 04 May 2026 L1 Ruby Yes Details →
2.19.4 18 Apr 2026 L1 Ruby Yes Details →
2.19.3 25 Mar 2026 L1 Ruby Yes Details →
2.15.2.1 18 Mar 2026 L1 Ruby Yes Details →
2.17.1.2 18 Mar 2026 L1 Ruby Yes Details →
2.19.2 18 Mar 2026 L1 Ruby Yes Details →
2.19.1 08 Mar 2026 H1 L1 Ruby Yes Details →
2.19.0 06 Mar 2026 H1 L1 Ruby Yes Details →
2.18.1 03 Feb 2026 H1 L1 Ruby Yes Details →
2.18.0 11 Dec 2025 H1 L1 Ruby Yes Details →
2.17.1 04 Dec 2025 L1 Ruby Yes Details →
2.17.0 03 Dec 2025 L1 Ruby Yes Details →
2.16.0 07 Nov 2025 L1 Ruby Yes Details →
2.15.2 25 Oct 2025 L1 Ruby Yes Details →
2.15.1 07 Oct 2025 L1 Ruby Yes Details →
2.15.0 22 Sep 2025 L1 Ruby Yes Details →
2.14.1 18 Sep 2025 L1 Ruby Yes Details →
2.14.0 18 Sep 2025 L1 Ruby Yes Details →
2.13.2 28 Jul 2025 L1 Ruby Yes Details →
2.13.1 24 Jul 2025 L1 Ruby Yes Details →
2.13.0 17 Jul 2025 L1 Ruby Yes Details →
2.12.2 23 May 2025 L1 Ruby Yes Details →
2.12.1 23 May 2025 L1 Ruby Yes Details →
2.12.0 12 May 2025 L1 Ruby Yes Details →
2.11.3 25 Apr 2025 L1 Ruby Yes Details →
2.11.2 24 Apr 2025 L1 Ruby Yes Details →
2.11.1 24 Apr 2025 L1 Ruby Yes Details →
2.11.0 24 Apr 2025 L1 Ruby Yes Details →
2.10.2 12 Mar 2025 L1 Ruby Yes Details →
2.10.1 10 Feb 2025 H1 L1 Ruby Yes Details →
2.10.0 10 Feb 2025 H1 L1 Ruby Yes Details →
2.9.1 18 Dec 2024 L1 Ruby Yes Details →
2.9.0 03 Dec 2024 L1 Ruby Yes Details →
2.8.2 14 Nov 2024 none Ruby — Details →
2.8.1 06 Nov 2024 none Ruby — Details →
2.8.0 06 Nov 2024 none Ruby — Details →
2.8.0.alpha1 06 Nov 2024 none Ruby — Details →
2.7.6 04 Nov 2024 none Ruby — Details →
2.7.5 30 Oct 2024 none Ruby — Details →
2.7.4 25 Oct 2024 none Ruby — Details →
2.7.4.rc2 25 Oct 2024 none Ruby — Details →
2.7.4.rc1 25 Oct 2024 none Ruby — Details →
2.7.3 24 Oct 2024 none Ruby — Details →
2.7.3.rc1 23 Oct 2024 none Ruby — Details →
2.7.2 04 Apr 2024 none Ruby — Details →
2.7.1 05 Dec 2023 none Ruby — Details →
2.7.0 01 Dec 2023 none Ruby — Details →
2.6.3 05 Dec 2022 none Ruby — Details →
2.6.2 16 May 2022 none Ruby — Details →
2.6.1 24 Oct 2021 none Ruby — Details →
2.6.0 14 Oct 2021 none Ruby — Details →
2.5.1 22 Dec 2020 none Ruby — Details →
2.5.0 22 Dec 2020 none Ruby — Details →
2.4.1 17 Dec 2020 none Ruby — Details →
2.4.0 15 Dec 2020 none Ruby — Details →
2.3.1 30 Jun 2020 none Ruby — Details →
2.3.0 11 Dec 2019 none Ruby — Details →
2.2.0 21 Feb 2019 H1 Ruby Yes Details →
2.1.0 18 Apr 2017 H1 Ruby Yes Details →
2.0.4 11 Apr 2017 H1 Ruby Yes Details →
1.8.6 13 Jan 2017 H1 Ruby Yes Details →
2.0.3 12 Jan 2017 H1 Ruby Yes Details →
1.8.5 12 Jan 2017 H1 Ruby Yes Details →
2.0.2 26 Jul 2016 H1 Ruby Yes Details →
2.0.1 01 Jul 2016 H1 Ruby Yes Details →
2.0.0 01 Jul 2016 H1 Ruby Yes Details →
1.8.3 02 Jun 2015 H1 Ruby Yes Details →
1.8.2 09 Jan 2015 H1 Ruby Yes Details →
1.8.1 17 Oct 2013 H1 Ruby Yes Details →
1.8.0 13 May 2013 H1 Ruby Yes Details →
1.7.7 11 Feb 2013 H1 Ruby Yes Details →
1.6.8 11 Feb 2013 H1 — Yes Details →
1.5.5 11 Feb 2013 H1 — Yes Details →
1.7.6 31 Dec 2012 H1 — Yes Details →
1.7.5 17 Aug 2012 H1 — Yes Details →
1.7.4 26 Jul 2012 H1 — Yes Details →
1.7.3 11 May 2012 H1 — Yes Details →
1.7.2 11 May 2012 H1 — Yes Details →
1.7.1 07 May 2012 H1 — Yes Details →
1.7.0 28 Apr 2012 H1 — Yes Details →
1.6.7 28 Apr 2012 H1 — Yes Details →
1.6.6 26 Mar 2012 H1 — Yes Details →
1.6.5 15 Jan 2012 H1 — Yes Details →
1.6.4 24 Dec 2011 H1 — Yes Details →
1.6.3 01 Dec 2011 H1 — Yes Details →
1.6.2 28 Nov 2011 H1 — Yes Details →
1.6.1 18 Sep 2011 H1 — Yes Details →
1.6.0 12 Sep 2011 H1 — Yes Details →
1.5.4 31 Aug 2011 H2 — Yes Details →
1.5.3 20 Jun 2011 H2 — Yes Details →
1.5.2 14 Jun 2011 H2 — Yes Details →
1.5.1 26 Jan 2011 H2 — Yes Details →
1.5.0 22 Jan 2011 H2 — Yes Details →
1.4.6 09 Aug 2010 H2 — Yes Details →
1.4.5 07 Aug 2010 H2 — Yes Details →
1.4.4 06 Aug 2010 H2 — Yes Details →
1.4.3 05 May 2010 H2 — Yes Details →
1.4.2 27 Apr 2010 H2 — Yes Details →
1.4.1 25 Apr 2010 H2 — Yes Details →
1.4.0 23 Apr 2010 H2 — Yes Details →
1.2.4 08 Apr 2010 H2 — Yes Details →
1.2.3 11 Mar 2010 H2 — Yes Details →
1.2.2 28 Feb 2010 H2 — Yes Details →
1.2.1 26 Feb 2010 H2 — Yes Details →
1.2.0 08 Nov 2009 H2 — Yes Details →
1.1.9 24 Sep 2009 H2 — Yes Details →
1.1.8 24 Sep 2009 H2 — Yes Details →

The newest 120 of 137 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 1
  • 2020 1
  • 2025 1
  • 2026 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 3 of the 6 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for json

The 5 most severe of 6 vulnerabilities recorded for this package

Search all 6 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-33210: Ruby JSON Format String Injection Vulnerability 8.3 high 2.19.2 19 Mar 2026
CVE-2020-10663: Unsafe object creation in json RubyGem 7.5 high 2.3.0 27 Jul 2020
CVE-2025-27788: Out-of-Bounds Read Vulnerability in Ruby JSON Parser 7.5 high 2.10.2 12 Mar 2025
CVE-2026-54696: Ruby json Package Heap Buffer Overflow Vulnerability 3.7 low 2.19.9 23 Jul 2026
CVE-2013-0269: JSON gem Improper Input Validation vulnerability N/A high 1.5.5 24 Oct 2017

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About json

Is json safe to use?

Vulert records 6 vulnerabilities for json in RubyGems: 0 critical, 4 high, 0 medium and 2 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is json's Vulert package health score?

Vulert scores json 79/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of json affected?

No. 3.1.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of json should I use?

3.1.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does json have?

6 vulnerabilities are recorded for json in the RubyGems ecosystem: 0 critical, 4 high, 0 medium and 2 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new json vulnerabilities disclosed?

3 vulnerabilities were recorded for json in the last 12 months, and the oldest entry in this database dates to 24 Oct 2017. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of json are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor json for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the json version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.