Google::Auth versions from 0.11 through 0.12 for Perl accept an authorization code from any local process because the
Source GCVE Database
Not known to be exploited.
Data as of 1 Nov 2026, 19:01 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or noneExploitation evidence
Disclosed: evidence found.
CVE published 1 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Google-Auth | Affected
| Fixed in– |
CPANGoogle-Authpkg:cpan/Google-AuthOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
Google::Auth versions 0.11 through 0.12 for Perl have a vulnerability where the gcloud-auth login callback does not verify the OAuth state parameter. This allows any local process to submit an authorization code, which the CLI exchanges and stores as the user's credentials, causing the user's tools to act as the attacker's account.