CVE-2026-66901
Received Received - Intake

Server-Side Request Forgery in Google::Auth for Perl

Vulnerability report for CVE-2026-66901, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-04

Last updated on: 2026-08-04

Assigner: CPANSec

Description

Google::Auth versions before 0.09 for Perl allow server side request forgery and credential exfiltration via unvalidated URLs taken from the credentials JSON. The URLs the library requests are read from the credentials JSON, and their hosts were not checked against the universe domain before the request. For an external_account configuration, retrieve_subject_token fetched credential_source.url with headers from the same JSON, and fetch_access_token posted the subject token to token_url, then sent the STS access token it received to service_account_impersonation_url in an Authorization: Bearer header. The authorized_user, impersonated_service_account and service_account configurations posted the client secret and refresh token, the source access token, and a signed JWT assertion to their own JSON-supplied token_uri or impersonation URL. Any caller that builds credentials from a configuration it does not fully control issues those requests from the application's network position, reaching hosts the configuration names, including internal services and link-local metadata endpoints, and hands them the credentials each request carries. The service_account assertion is bound to aud, so it is not replayable against Google. Version 0.06 added a _validate_url host check to the external_account class, keyed on a universe_domain read from the same credentials JSON. Version 0.07 gated a JSON-supplied universe domain behind GOOGLE_EXTERNAL_ACCOUNT_ALLOW_CUSTOM_UNIVERSES=1, deriving the pin flag from arguments that an earlier BUILDARGS pass had already merged on the make_creds path. Version 0.08 passed the pin decision through as an explicit constructor argument and moved _validate_url to Google::Auth::Credentials, adding the call to UserRefreshCredentials and ImpersonatedServiceAccountCredentials, and 0.09 added it to ServiceAccountCredentials.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-04
Last Modified
2026-08-04
Generated
2026-08-05
AI Q&A
2026-08-05
EPSS Evaluated
N/A
NVD

Affected Vendors & Products

Showing 4 associated CPEs
Vendor Product Version / Range
google auth to 0.09 (exc)
google auth to 0.08 (exc)
google auth to 0.07 (exc)
google auth to 0.06 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
CWE-201 The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in Google::Auth versions before 0.09 for Perl allows server side request forgery and credential exfiltration through unvalidated URLs from credentials JSON. The library requests URLs read from the credentials JSON without checking hosts against the universe domain. This enables attackers to send credentials to internal services or link-local endpoints controlled by the configuration.

Detection Guidance

This vulnerability involves server-side request forgery and credential exfiltration via unvalidated URLs in Google::Auth versions before 0.09 for Perl. Detection requires checking installed versions of Google::Auth and reviewing configurations for external_account, authorized_user, impersonated_service_account, and service_account settings that may use untrusted URLs.

Impact Analysis

If you use Google::Auth versions before 0.09, an attacker could exploit this to steal credentials or make unauthorized requests from your application's network position. This could lead to data breaches, unauthorized access to services, or further network compromise.

Compliance Impact

This vulnerability could lead to unauthorized data access or exfiltration, violating GDPR's data protection principles or HIPAA's security requirements. Organizations may face compliance violations, fines, or reputational damage if credentials are compromised due to this issue.

Mitigation Strategies

Upgrade Google::Auth to version 0.09 or later to address the vulnerability. Review and validate all credential configurations, especially those using external_account, to ensure URLs are properly checked against the universe domain. Remove or restrict configurations that allow custom universes unless explicitly required.

Chat Assistant

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

EPSS Chart