Is ruby_parser 2.0 vulnerable?

RubyGems · 7 releases from 2.0.0 to 2.0.6 · latest ruby_parser is 3.22.0 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. ruby_parser 2.0.6, the last 2.0 release, is affected by 1 known security advisory (1 low), including CVE-2013-0162. Upgrade to 3.1.2 or later to fix all of them.

Upgrade with:bundle update --conservative ruby_parser # Gemfile: '>= 3.1.2'

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

Advisories affecting ruby_parser 2.0.6

  • 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 2.0.x release

Affected: 2.0.2 to 2.0.6. Latest ruby_parser: 3.22.0.

VersionKnown advisories
ruby_parser 2.0.6CVE-2013-0162
ruby_parser 2.0.5CVE-2013-0162
ruby_parser 2.0.4CVE-2013-0162
ruby_parser 2.0.3CVE-2013-0162
ruby_parser 2.0.2CVE-2013-0162
ruby_parser 2.0.1None
ruby_parser 2.0.0None

Which of your client projects are still on ruby_parser 2.0?

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.