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.
CVE-2026-54605
HIGHPre-NVD 7.27.2—Trending — 3 sources updated this week
EchelonGraph scoreMEDIUM confidence
This high-severity CVE scores 7.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 97% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.2Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.2
- EG Score
- 7.2(medium)
- EG Risk
- 37(Track)EG Risk 37/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity72% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 3%
- KEV
- Not listed
Published
July 28, 2026
Last Modified
July 28, 2026
Advisory Details (3)
Auto-updated Jul 28, 2026Patch available. Sources: github, github_commit, github_release.
github_release Patch Available
v1.1.6
Patch available: ruby-oauth/oauth v1.1.6
https://github.com/ruby-oauth/oauth/releases/tag/v1.1.6github_commit Patch Available
commit d069dc8c4c96 (ruby-oauth/oauth)
Patch available: ruby-oauth/oauth v1.1.6 (contains commit d069dc8c4c96)
https://github.com/ruby-oauth/oauth/commit/d069dc8c4c9631947451215f07460d6cdf0caf3fgithub Patch Available
Cross-origin OAuth token-request redirects can expose signed request metadata · Advisory · ruby-oauth/oauth · GitHub
https://github.com/ruby-oauth/oauth/security/advisories/GHSA-prq8-7wvh-44qhVendor Advisories for CVE-2026-54605(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-30 03:12 UTCEG score recompute
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-28 17:22 UTCEG score recompute
- 2026-07-28 16:53 UTCEG score recompute
- 2026-07-28 16:53 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-918 · CWE-346 · CWE-200
Frequently asked(5)
What is CVE-2026-54605?
CVE-2026-54605 is a high vulnerability published on July 28, 2026. 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…
When was CVE-2026-54605 disclosed?
CVE-2026-54605 was first published in the National Vulnerability Database on July 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54605 actively exploited?
CVE-2026-54605 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.8% of all scored CVEs.
What is the CVSS score of CVE-2026-54605?
CVE-2026-54605 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2026-54605?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54605, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-54605
Is Your Infrastructure Affected by CVE-2026-54605?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.