CVE-2026-66901
HIGHDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 27% of all known CVEs.
References
Related Vulnerabilities
Other CWE-201 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2025-60188 | High | 7.5 | 3.5% | - | - |
| CVE-2022-27779 | Medium | 5.3 | 2.7% | - | Fix |
| CVE-2017-16026 | Medium | 5.9 | 2.6% | - | Fix |
| CVE-2017-2582 | Medium | 6.5 | 2.5% | - | Fix |
| CVE-2020-26085 | Critical | 9.9 | 2.2% | - | Fix |
| CVE-2024-32825 | High | 7.5 | 2.0% | - | - |
Common questions
How do I fix CVE-2026-66901?
No published fix for CVE-2026-66901 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-66901 being actively exploited?
Not that we know of. CVE-2026-66901 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.34% is the estimated probability that it will be exploited in the next 30 days. That is higher than 27% of all scored CVEs.
How severe is CVE-2026-66901?
CVE-2026-66901 has a CVSS v3 base score of 7.5, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-66901
Markdown
[](https://tridentstack.com/cve/CVE-2026-66901)HTML
<a href="https://tridentstack.com/cve/CVE-2026-66901"><img src="https://tridentstack.com/cve/badge/CVE-2026-66901.svg" alt="CVE-2026-66901"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-26.