VulnSocial

CVE-2026-74760

LOWCVSS 8.8 · HIGH

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD description

Google::Auth versions from 0.11 through 0.12 for Perl accept an authorization code from any local process because the gcloud-auth login callback does not check the OAuth state. The gcloud-auth login and application-default login commands send a state parameter with the authorization request, then take the code from the first request to reach their loopback listener without comparing the returned state. A local attacker can submit an authorization code for their own Google account. The CLI exchanges it and stores the refresh token as the user's credentials, so the user's tools then act as the attacker's account.

Back to dashboard
0.0/ 10 priority

Sources & remediation

Other references
Weakness type (CWE)
CWE-346

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

NONE

Threat summary

  • 1 mentions across 1 observed day

What's happening

  • 1 total mentions across 1 day

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-11-07: 111-07
Full discourse1 post
  • Upwind Security MDR@UpwindMDR

    🚨High - Google::Auth OAuth Loopback State Validation Bypass (CVE-2026-74760) Google::Auth (Perl) gcloud-auth loopback login callback fails to validate the OAuth state and accepts the first authorization code received. A local attacker can race the loopback listener and inject their own auth code, causing the CLI to store the attacker’s refresh token and run subsequent actions under the attacker’s Google account. 👉Affected: Google-Auth 0.11-0.12

    00010116
    395 followersView on X

Explore more

Back to dashboard