{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-66901 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-66901 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-66901 is a high-severity vulnerability in CJCOLLIER Google::Auth, published on 4 Aug 2026."},"fix_prompt":"Check this codebase for CVE-2026-66901 and fix it if it is affected.\n\nWhat it is: CVE-2026-66901 is a high-severity vulnerability in CJCOLLIER Google::Auth, published on 4 Aug 2026. \nExploitation: There is no known exploitation of CVE-2026-66901 in the wild and no public exploit code.\n\nAffected product: CJCOLLIER Google::Auth. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-66901/ (Markdown: https://insights.sbomify.com/CVE-2026-66901/index.md)","id":"CVE-2026-66901","markdown":"https://insights.sbomify.com/CVE-2026-66901/index.md","name":"CVE-2026-66901","record":{"aliases":["GHSA-xxpm-5c34-x4c3"],"analysis":null,"analysis_generated_by":null,"assigner":"CPANSec","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"},{"id":"CWE-201","name":"Insertion of Sensitive Information Into Sent Data"}],"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.\n\nThe 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.\n\nAny 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.\n\nVersion 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Google::Auth versions before 0.09 for Perl allow server side request forgery and credential exfiltration via unvalidated URLs taken from the credentials JSON.","id":"CVE-2026-66901","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Google::Auth versions before 0.06 for Perl run a command named in an external_account credentials JSON via an ungated system call.","id":"CVE-2026-66902"},"packages":[],"prev":{"headline":"Path traversal via unvalidated instance name in backup tarball restore enables root file write / RCE","id":"CVE-2026-66898"},"products":["Google::Auth"],"published":"2026-08-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-05","vendors":["CJCOLLIER"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-66901/"}