Is ruby-openid 1.0 vulnerable?

RubyGems · 3 releases from 1.0.0 to 1.0.2 · latest ruby-openid is 2.9.2 · checked 18 Nov 2026

Yes: 2 known advisories

Yes. ruby-openid 1.0.2, the last 1.0 release, is affected by 2 known security advisories (1 critical, 1 medium), including CVE-2019-11027, CVE-2013-1812. 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 1.0.2

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

    ruby-openid SSRF via claimed_id request

    Affected
    <2.9.0
    Fixed in
    2.9.0
  • MediumCVE-2013-1812GHSA-6c8p-qphv-668v24 Oct 2017

    Denial of service in ruby-openid

    Affected
    <2.2.2
    Fixed in
    2.2.2

Every ruby-openid 1.0.x release

Affected: 1.0.0 to 1.0.2. Latest ruby-openid: 2.9.2.

VersionKnown advisories
ruby-openid 1.0.2CVE-2019-11027, CVE-2013-1812
ruby-openid 1.0.1CVE-2019-11027, CVE-2013-1812
ruby-openid 1.0.0CVE-2019-11027, CVE-2013-1812

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

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.