CriticalGHSA-5c5f-7vfq-3732CVE-2022-32511

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

Published 7 Jun 2022 · Updated 10 Sept 2026

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

Affected package

jmespathRubyGems
Affected
<1.6.1
Fixed in
1.6.1
Update to the fixed version for your release line, for example:bundle update --conservative jmespath # Gemfile: '>= 1.6.1'

Details

jmespath.rb (aka JMESPath for Ruby) before 1.6.1 uses JSON.load in a situation where JSON.parse is preferable.

Is GHSA-5c5f-7vfq-3732 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected jmespath, and gives you the command that fixes it.

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.