Is json 1.2 vulnerable?

RubyGems · 5 releases from 1.2.0 to 1.2.4 · latest json is 3.1.0 · checked 18 Nov 2026

Yes: 2 known advisories

Yes. json 1.2.4, the last 1.2 release, is affected by 2 known security advisories (2 high), including CVE-2020-10663, CVE-2013-0269. Upgrade to 2.3.0 or later to fix all of them.

Upgrade with:bundle update --conservative json # Gemfile: '>= 2.3.0'

Is your project on an affected json?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting json 1.2.4

  • HighCVE-2020-10663GHSA-jphg-qwrw-7w9g27 Jul 2020

    Unsafe object creation in json RubyGem

    Affected
    <2.3.0
    Fixed in
    2.3.0
  • HighCVE-2013-0269GHSA-x457-cw4h-hq5f24 Oct 2017

    JSON gem has Improper Input Validation vulnerability

    Affected
    <1.5.5 · >=1.6.0 <1.6.8 · >=1.7.0 <1.7.7
    Fixed in
    1.5.5, 1.6.8, 1.7.7

Every json 1.2.x release

Affected: 1.2.0 to 1.2.4. Latest json: 3.1.0.

VersionKnown advisories
json 1.2.4CVE-2020-10663, CVE-2013-0269
json 1.2.3CVE-2020-10663, CVE-2013-0269
json 1.2.2CVE-2020-10663, CVE-2013-0269
json 1.2.1CVE-2020-10663, CVE-2013-0269
json 1.2.0CVE-2020-10663, CVE-2013-0269

Which of your client projects are still on json 1.2?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact json version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other json versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the RubyGems registry. Refreshed daily.