CVE-2026-74760

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

Published Nov 1, 2026 CVSS 3.1 · 8.8 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The Google::Auth module for Perl accepts an OAuth2 authorization code from any local process because the gcloud-auth login callback fails to verify the OAuth state returned by the provider. This omission allows a local attacker to supply a valid code from the attacker's own Google account. When the CLI exchanges the code, it stores the resulting refresh token as the user’s credentials, meaning subsequent operations performed with the user’s tools will act on behalf of the attacker’s account.

Affected Systems

Affected systems are installations of the Google::Auth CPAN module for Perl, specifically version 0.11 and 0.12. Any environment that invokes the gcloud‑auth CLI in these versions is vulnerable. Users who have updated their module or replaced it with a newer release beyond 0.12 are not affected by this flaw.

Risk and Exploitability

The vulnerability requires local access to the machine running the CLI or the ability to launch a process that can listen on the loopback interface used by gcloud-auth. The lack of an implemented state check means exploitation is straightforward for any local attacker and can occur without network connectivity. The CVSS score is 8.8, indicating high severity, and the EPSS score is <1%, suggesting a low probability of exploitation. The issue is not yet listed in CISA’s KEV catalog. Nevertheless, the flaw allows complete credential hijacking; once a malicious refresh token is stored, all commands executed by the affected tools will run as the attacker’s Google account. The risk is therefore high in environments where local code execution or untrusted processes can run on the user’s workstation or server.

Remediation

Vendor Solution

Upgrade to a future Google-Auth release.


Vendor Workaround

Run gcloud-auth login and gcloud-auth application-default login with --no-browser, which uses the out-of-band flow without a loopback listener.


OpenCVE Recommended Actions

  • Upgrade the Google::Auth module to a version newer than 0.12, where the OAuth state validation has been corrected.
  • Until an update is possible, use the gcloud-auth CLI with the --no-browser flag for both login and application-default login, which forces the out‑of‑band flow and does not use a local loopback listener.
  • After applying the upgrade or workaround, revoke any existing user credentials that may have been compromised and re‑authorize with a fresh consent prompt to ensure only legitimate tokens are stored.

Generated by OpenCVE AI on November 6, 2026 at 16:48 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

Type Values Removed Values Added
First Time appeared Perl
Perl google::auth
Vendors & Products Perl
Perl google::auth
Type Values Removed Values Added
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.
Title 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
Weaknesses CWE-346
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
CPANSec
Published
Updated
Nov 6, 2026, 2:59 PM
Reserved
Aug 15, 2026, 12:28 PM
Status
Awaiting Analysis
Published
Nov 1, 2026, 5:16 PM
Modified
Nov 6, 2026, 3:17 PM