Is omniauth 2.0 vulnerable?
RubyGems · 5 releases from 2.0.0 to 2.0.4 · latest omniauth is 2.4.2 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. omniauth 2.0.4, the last 2.0 release, is affected by 1 known security advisory (1 medium), including CVE-2026-63183. Upgrade to 2.2.0 or later to fix all of them.
bundle update --conservative omniauth # Gemfile: '>= 2.2.0'Is your project on an affected omniauth?
Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting omniauth 2.0.4
OmniAuth: Host Header Injection Vulnerability
- Affected
- <2.2.0
- Fixed in
- 2.2.0
Every omniauth 2.0.x release
Affected: 2.0.0 to 2.0.4. Latest omniauth: 2.4.2.
| Version | Known advisories |
|---|---|
| omniauth 2.0.4 | CVE-2026-63183 |
| omniauth 2.0.3 | CVE-2026-63183 |
| omniauth 2.0.2 | CVE-2026-63183 |
| omniauth 2.0.1 | CVE-2026-63183 |
| omniauth 2.0.0 | CVE-2026-63183 |
Which of your client projects are still on omniauth 2.0?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact omniauth version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other omniauth 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.