PatchSiren cyber security CVE debrief
CVE-2026-74759 CJCOLLIER CVE debrief
CVE-2026-74759 debrief: Google::Auth Perl library versions 0.12 is vulnerable to server-side request forgery via unvalidated credential_source URLs in AWS external account credentials. An external_account configuration with the AWS subject token type selects Google::Auth::ExternalAccountCredentials::Aws. Its retrieve_subject_token sends requests to the imdsv2_session_token_url, url and region_url fields of credential_source without the host check that the other credential classes apply. This oversight allows attackers to potentially access internal services and metadata endpoints, leading to unauthorized data breaches and lateral movement within compromised networks. Defenders of 3
- Vendor
- CJCOLLIER
- Product
- Google-Auth
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-11-01
- Original CVE updated
- 2026-11-01
- Advisory published
- 2026-11-01
- Advisory updated
- 2026-11-01
Who should care
Defenders of systems using Google::Auth Perl library, especially those with AWS external account credentials, should assess exposure and verify credential_source URL validation to prevent potential server-side request forgery attacks.
Why it matters
CVE-2026-74759 allows server-side request forgery in Google::Auth Perl library, impacting defenders of systems using AWS external account credentials. They must assess exposure, verify credential_source URL validation, and restrict access to internal services and metadata endpoints.
- Potential unauthorized access to internal services
- Possible data breaches via metadata endpoints
- Risk of lateral movement within compromised networks
- Need for verification of credential_source URL validation
Technical summary
Google::Auth versions 0.12 for Perl allow server-side request forgery via unvalidated credential_source URLs in AWS external account credentials. An external_account configuration with the AWS subject token type selects Google::Auth::ExternalAccountCredentials::Aws. Its retrieve_subject_token sends requests to the imdsv2_session_token_url, url and region_url fields of credential_source without the host check that the other credential classes apply.
Defensive priority
Assess exposure in Google::Auth Perl library usage, verify credential_source URL validation, and restrict access to internal services and metadata endpoints.
Recommended defensive actions
- Assess exposure in Google::Auth Perl library usage
- Verify credential_source URL validation
- Restrict access to internal services and metadata endpoints
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The CVE record and NVD entry provide details on the vulnerability in Google::Auth versions 0.12 for Perl, allowing server-side request forgery via unvalidated credential_source URLs in AWS external account credentials.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-74759 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-74759
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-74759 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-74759
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://metacpan.org/release/CJCOLLIER/Google-Auth-0.12/source/lib/Google/Auth/ExternalAccountCredentials/Aws.pm
9b29abf9-4ab0-4765-b253-1875cd9b441e
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.