Is oauth2 0.8 vulnerable?

RubyGems · 2 releases from 0.8.0 to 0.8.1 · latest oauth2 is 2.1.0 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. oauth2 0.8.1, the last 0.8 release, is affected by 1 known security advisory (1 high), including CVE-2026-54603. Upgrade to 2.0.22 or later to fix all of them.

Upgrade with:bundle update --conservative oauth2 # Gemfile: '>= 2.0.22'

Is your project on an affected oauth2?

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 oauth2 0.8.1

  • HighCVE-2026-54603GHSA-pp92-crg2-gfv928 Jul 2026

    OAuth2::Client#request: Protocol-relative redirect Location overrides authority, leaking bearer Authorization to attacker host

    Affected
    >=0.4.0 <2.0.22
    Fixed in
    2.0.22

Every oauth2 0.8.x release

Affected: 0.8.0 to 0.8.1. Latest oauth2: 2.1.0.

VersionKnown advisories
oauth2 0.8.1CVE-2026-54603
oauth2 0.8.0CVE-2026-54603

Which of your client projects are still on oauth2 0.8?

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

Other oauth2 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.