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.
bundle update --conservative oauth # Gemfile: '>= 1.1.9'Is your project on an affected oauth?
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
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.
| Version | Known advisories |
|---|---|
| oauth 1.1.9 | None |
| oauth 1.1.8 | None |
| oauth 1.1.7 | None |
| oauth 1.1.6 | None |
| oauth 1.1.5 | CVE-2026-54605 |
| oauth 1.1.4 | CVE-2026-54605 |
| oauth 1.1.3 | CVE-2026-54605 |
| oauth 1.1.2 | CVE-2026-54605 |
| oauth 1.1.1 | CVE-2026-54605 |
| oauth 1.1.0 | CVE-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.