Is jmespath 1.0 vulnerable?

RubyGems · 3 releases from 1.0.0 to 1.0.2 · latest jmespath is 1.6.2 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. jmespath 1.0.2, the last 1.0 release, is affected by 1 known security advisory (1 critical), including CVE-2022-32511. Upgrade to 1.6.1 or later to fix all of them.

Upgrade with:bundle update --conservative jmespath # Gemfile: '>= 1.6.1'

Is your project on an affected jmespath?

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 jmespath 1.0.2

  • CriticalCVE-2022-32511GHSA-5c5f-7vfq-37327 Jun 2022

    JMESPath for Ruby uses unsafe JSON.load when safe JSON.parse is preferable

    Affected
    <1.6.1
    Fixed in
    1.6.1

Every jmespath 1.0.x release

Affected: 1.0.0 to 1.0.2. Latest jmespath: 1.6.2.

VersionKnown advisories
jmespath 1.0.2CVE-2022-32511
jmespath 1.0.1CVE-2022-32511
jmespath 1.0.0CVE-2022-32511

Which of your client projects are still on jmespath 1.0?

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

Other jmespath 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.