Is ruby-openid 1.1 vulnerable?
RubyGems · 4 releases from 1.1.1 to 1.1.4 · latest ruby-openid is 2.9.2 · checked 18 Nov 2026
Yes: 2 known advisories
Yes. ruby-openid 1.1.4, the last 1.1 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.
bundle update --conservative ruby-openid # Gemfile: '>= 2.9.0'Is your project on an affected ruby-openid?
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.1.4
ruby-openid SSRF via claimed_id request
- Affected
- <2.9.0
- Fixed in
- 2.9.0
Denial of service in ruby-openid
- Affected
- <2.2.2
- Fixed in
- 2.2.2
Every ruby-openid 1.1.x release
Affected: 1.1.1 to 1.1.4. Latest ruby-openid: 2.9.2.
| Version | Known advisories |
|---|---|
| ruby-openid 1.1.4 | CVE-2019-11027, CVE-2013-1812 |
| ruby-openid 1.1.3 | CVE-2019-11027, CVE-2013-1812 |
| ruby-openid 1.1.2 | CVE-2019-11027, CVE-2013-1812 |
| ruby-openid 1.1.1 | CVE-2019-11027, CVE-2013-1812 |
Which of your client projects are still on ruby-openid 1.1?
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.