Is oauth 1.1 vulnerable?

RubyGems · 10 releases from 1.1.0 to 1.1.9 · latest oauth is 1.1.9 · checked 18 Nov 2026

No known advisories in the last release

oauth 1.1.9, the last 1.1 release, has no known advisories. 1 advisory affects earlier 1.1.x releases, so update to 1.1.9.

Update within 1.1:bundle update --conservative oauth # Gemfile: '>= 1.1.9'

Is your project on an affected oauth?

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

Fixed within 1.1.x, affecting earlier releases

  • HighCVE-2026-54605GHSA-prq8-7wvh-44qh28 Jul 2026

    OAuth: Cross-origin token-request redirects can expose signed request metadata

    Affected
    >=0.5.5 <1.1.6
    Fixed in
    1.1.6

Every oauth 1.1.x release

Affected: 1.1.0 to 1.1.5. 1.1.6 and later are not affected.

VersionKnown advisories
oauth 1.1.9None
oauth 1.1.8None
oauth 1.1.7None
oauth 1.1.6None
oauth 1.1.5CVE-2026-54605
oauth 1.1.4CVE-2026-54605
oauth 1.1.3CVE-2026-54605
oauth 1.1.2CVE-2026-54605
oauth 1.1.1CVE-2026-54605
oauth 1.1.0CVE-2026-54605

Which of your client projects are still on oauth 1.1?

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

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