CVE-2026-74760
Received Received - Intake

OAuth State Not Validated in Google::Auth for Perl

Publication date: 2026-11-01

Last updated on: 2026-11-01

Assigner: CPANSec

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-01
Last Modified
2026-11-01
Generated
2026-11-01
AI Q&A
2026-11-01
EPSS Evaluated
N/A
NVD
CVE-2026-74760

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
google auth From 0.11 (inc) to 0.12 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-346 The product does not properly verify that the source of data or communication is valid.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects Google::Auth versions 0.11 through 0.12 for Perl. The gcloud-auth login callback does not verify the OAuth state parameter, allowing any local process to submit an authorization code. The CLI accepts the first code received without checking its origin, enabling an attacker to inject their own credentials and gain access to the user's account.

Detection Guidance

Check for unauthorized gcloud-auth.pl processes running on your system. Look for unexpected network listeners on 127.0.0.1 using commands like netstat -tuln or ss -tuln. Inspect file permissions on Google Auth credential storage paths for unauthorized access.

Impact Analysis

An attacker with local access could trick the gcloud-auth tool into storing their Google account credentials as yours. This means your tools would then act on behalf of the attacker's account, potentially accessing your data or resources without your knowledge.

Compliance Impact

This vulnerability could lead to unauthorized access to user credentials and sensitive data, potentially violating GDPR's data protection requirements and HIPAA's safeguards for protected health information if credentials grant access to such data.

Mitigation Strategies

Update Google::Auth to a patched version if available. Restrict local process access to gcloud-auth.pl. Review and remove any unauthorized credentials stored in predictable file paths. Monitor for suspicious OAuth authorization code submissions.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-74760. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...