Information Disclosure in oauth (CVE-2026-54605)
Summary
Vulnerability in oauth (CVE-2026-54605). Risk of unauthorized operations or information disclosure. Exploitable via Location. Mitigation: upgrade to 1.1.6 or later.
Original description
The description as published by the source.
Cross-origin OAuth token-request redirects can expose signed request metadata
Summary
When an application uses OAuth::Consumer to request OAuth 1.0 request tokens or
access tokens, the token request helper follows 300..399 redirects returned by
the OAuth server. In affected versions, OAuth::Consumer#token_request parses the
raw Location header, follows the redirect recursively, and can mutate the
consumer's configured site when the redirect points to a different host with
the same path.
The result is a cross-origin signed-request disclosure primitive: if an OAuth
server token endpoint returns a redirect whose target an attacker controls, the
client can re-sign the token request and send OAuth 1.0 request metadata,
including the OAuth signature, nonce, timestamp, consumer key, and any request
parameters included in the signature base string, to the attacker-controlled
host. The same behavior can also be used as an SSRF or confused-deputy primitive
because the application server follows the redirect and sends the next request
from its own network position.
Affected
oauthv1.1.5 and prior versions back to and including v0.5.5.- The cross-host token redirect behavior was introduced by
https://github.com/ruby-oauth/oauth/commit/d74b767f - The behavior is documented in the v0.5.5 changelog as "Allow redirect to
different host but same path".
- The cross-host token redirect behavior was introduced by
- The vulnerable behavior is in
OAuth::Consumer#token_request, which is used by
the documented req…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54605 has been found in oauth.
Attackers can target a specific entry point like Location over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.2/10.
What to do: upgrade oauth to 1.1.6 or later.
If unsure, ask your IT team or search "oauth CVE-2026-54605" on the vendor's site.
CVE-2026-54605 (oauth) — CWE-200 / CVSS v3 7.2
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: Location / site / oauth / oauth_consumer_key
Patched: 1.1.6 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Information disclosure (CWE-200) exists in oauth. Attackers reach the vulnerable code path via Location without authentication.
Check the vendor advisory for the affected versions of oauth. Attack surface: Location / site / oauth / oauth_consumer_key.
Severity: High (CVSS 7.2/10). Risk of unauthorized operations or information disclosure.
Update to 1.1.6.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'oauth' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'oauth' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
oauthを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade oauth to 1.1.6ステージング環境で 1.1.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Ubuntu UBUNTU-CVE-2026-54605 ruby-oauth
References
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com