GEM · JULY 2026 · EARLY WARNING

OAuth Gem for Ruby: Cross-Origin Redirects May Expose Metadata

EARLY WARNING · UNCONFIRMED. This page describes a developing threat that 0Day surfaced from early signals and has not yet independently confirmed. Details may change. Always verify against the primary sources before acting.

GHSA-PRQ8-7WVH-44QHSeverity: HIGH

Reportedly, the OAuth gem for Ruby <=1.1.5 can expose signed request metadata in cross-origin token-request redirects, potentially leading to SSRF or confused-deputy attacks.

What happened

An early warning has been issued regarding a potential vulnerability in the OAuth gem for Ruby, versions <=1.1.5. The issue reportedly involves cross-origin token-request redirects that may expose signed request metadata. This exposure could potentially lead to server-side request forgery (SSRF) or confused-deputy attacks. To assess your exposure, check if your application uses the affected versions of the OAuth gem. It is recommended to upgrade to OAuth v1.1.6 or later to mitigate the risk. The primary source for this advisory is GHSA-PRQ8-7WVH-44QH on GitHub.

How 0Day mitigates this

MATCHED TO YOUR ACTUAL DEPENDENCY GRAPH0Day matches every incoming threat signal against your GitHub organization’s full dependency graph, including transitive dependencies. If oauth is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.

Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.

Join the 0Day waitlist →

← Back to all threats