Is oauth 0.2 vulnerable?

RubyGems · 6 releases from 0.2.0 to 0.2.7 · latest oauth is 1.1.9 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. oauth 0.2.7, the last 0.2 release, is affected by 1 known security advisory (1 high), including CVE-2016-11086. Upgrade to 0.5.5 or later to fix all of them.

Upgrade with:bundle update --conservative oauth # Gemfile: '>= 0.5.5'

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

Advisories affecting oauth 0.2.7

  • HighCVE-2016-11086GHSA-7359-3c6r-hfc222 Apr 2021

    Improper Certificate Validation in oauth ruby gem

    Affected
    <0.5.5
    Fixed in
    0.5.5

Every oauth 0.2.x release

Affected: 0.2.0 to 0.2.7. Latest oauth: 1.1.9.

VersionKnown advisories
oauth 0.2.7CVE-2016-11086
oauth 0.2.6CVE-2016-11086
oauth 0.2.4CVE-2016-11086
oauth 0.2.2CVE-2016-11086
oauth 0.2.1CVE-2016-11086
oauth 0.2.0CVE-2016-11086

Which of your client projects are still on oauth 0.2?

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.