Answer in brief
CVE-2026-74760 records a Unknown severity vulnerability in 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 current sources do not mark it as known exploited. The current feed maps Google-Auth (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Google-Auth (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Google-Authgeneric | >=0.11 <=0.12 | Not reported |
Published upstream
Nov 1, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 1, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 1, 2026
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.
Quoted source text, attributed separately from HOL analysis.