CVE-2026-54605 OAuth: Cross-origin token-request redirects can expose signed request metadata
Attackers can expose signed OAuth request metadata to cross-origin hosts via malicious redirects in the Ruby OAuth library.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-54605?
CVE-2026-54605 is a high-severity server-side request forgery vulnerability in ruby-oauth oauth, published on 28 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
OAuth is a Ruby wrapper for the OAuth 1.0 and 1.0a protocols, providing clients and servers. From 0.5.5 to 1.1.5, OAuth::Consumer#token_request parses the raw Location header of a 300 to 399 redirect returned by the OAuth server and follows the redirect recursively, which can mutate the consumer's configuration and expose signed OAuth request metadata, including the Authorization header, to a cross-origin host. This issue is fixed in version 1.1.6.
Which versions are affected by CVE-2026-54605?
2 open source packages ship an affected version, including oauth.
| Package | Affected | Fixed in |
|---|---|---|
oauth RubyGems | From 0.5.5 | 1.1.6 |
oauth RubyGems | From 0.5.5 | 1.1.6 |
How do I fix CVE-2026-54605?
Upgrade oauth to 1.1.6 or later.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2026-54605 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54605 exists.
Sources
Also known as GHSA-prq8-7wvh-44qh, UBUNTU-CVE-2026-54605.