Is ruby_parser 3.1 vulnerable?

RubyGems · 4 releases from 3.1.0 to 3.1.3 · latest ruby_parser is 3.22.0 · checked 18 Nov 2026

No known advisories in the last release

ruby_parser 3.1.3, the last 3.1 release, has no known advisories. 1 advisory affects earlier 3.1.x releases, so update to 3.1.3.

Update within 3.1:bundle update --conservative ruby_parser # Gemfile: '>= 3.1.3'

Is your project on an affected ruby_parser?

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

Fixed within 3.1.x, affecting earlier releases

  • LowCVE-2013-0162GHSA-8mvw-22r7-w6fq5 May 2022

    ruby_parser allows local users to overwrite arbitrary files via symlink attack on temporary file with predictable name

    Affected
    >=2.0.2 <3.1.2
    Fixed in
    3.1.2

Every ruby_parser 3.1.x release

Affected: 3.1.0 to 3.1.1. 3.1.2 and later are not affected. Latest ruby_parser: 3.22.0.

VersionKnown advisories
ruby_parser 3.1.3None
ruby_parser 3.1.2None
ruby_parser 3.1.1CVE-2013-0162
ruby_parser 3.1.0CVE-2013-0162

Which of your client projects are still on ruby_parser 3.1?

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

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