Is ruby-openid 2.7 vulnerable?

RubyGems · 1 release from 2.7.0 to 2.7.0 · latest ruby-openid is 2.9.2 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. ruby-openid 2.7.0, the last 2.7 release, is affected by 1 known security advisory (1 critical), including CVE-2019-11027. Upgrade to 2.9.0 or later to fix all of them.

Upgrade with:bundle update --conservative ruby-openid # Gemfile: '>= 2.9.0'

Is your project on an affected ruby-openid?

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-openid 2.7.0

  • CriticalCVE-2019-11027GHSA-fqfj-cmh6-hj4913 Jun 2019

    ruby-openid SSRF via claimed_id request

    Affected
    <2.9.0
    Fixed in
    2.9.0

Which of your client projects are still on ruby-openid 2.7?

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

Other ruby-openid 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.