omniauth vulnerabilities

A generalized Rack framework for multiple-provider authentication.

Registry
RubyGems
Latest
2.4.2
License
MIT

4 known advisories

The latest version, 2.4.2, is not affected by any of them. Projects on older versions may be.

Update to the latest version:bundle update --conservative omniauth # Gemfile: '>= 2.4.2'

Is your project on an affected omniauth?

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

Security advisories for omniauth

  • MediumCVE-2026-63183GHSA-m27g-v28p-f9fx9 Nov 2026

    OmniAuth: Host Header Injection Vulnerability

    Affected
    <2.2.0
    Fixed in
    2.2.0
  • CriticalCVE-2020-36599GHSA-pm55-qfxr-h24719 Aug 2022

    OmniAuth's `lib/omniauth/failure_endpoint.rb` does not escape `message_key` value

    Affected
    <1.9.2 · >=2.0.0.pre.rc1 <2.0.0
    Fixed in
    1.9.2, 2.0.0
  • HighCVE-2015-9284GHSA-ww4x-rwq6-qpgf29 May 2019

    OmniAuth Ruby gem Cross-site Request Forgery in request phase

    Affected
    <2.0.0
    Fixed in
    2.0.0
  • HighCVE-2017-18076GHSA-9pr6-grf4-x2fr29 Jan 2018

    Omniauth allows POST parameters to be stored in session

    Affected
    <1.3.2
    Fixed in
    1.3.2

Is your omniauth version vulnerable?

Which of your client projects still run an old omniauth?

NPMscan reads the Gemfile.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

Other RubyGems packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the RubyGems registry.