VulnerabilityPublished 1 Nov 2026

CVE-2026-74759: Google-Auth (Perl module) · Server-Side Request Forgery

Affects Google-Auth (Perl module)Source CVE Database V5

Compare

Not known to be exploited · patch available : patch Google-Auth (Perl module) soon.

Data as of 1 Nov 2026, 17:13 UTC

Severity

High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Patch: Available

Exploitation evidence

Disclosed: evidence found.
CVE published 1 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Google-Auth	Affected =0.12	Fixed in–
CPANGoogle-Auth`pkg:cpan/Google-Auth`Other threats	Affected =0.12	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available for this vulnerability. Users of Google::Auth version 0.12 should apply the official fix to ensure proper validation of credential_source URLs. Since this is a cloud service library, the vendor manages remediation for cloud-hosted services; users should consult the vendor advisory for confirmation and apply updates accordingly.

Description

Google::Auth version 0.12 for Perl contains a server-side request forgery (SSRF) vulnerability due to unvalidated URLs in AWS external account credentials. This flaw allows attackers to make unauthorized HTTP GET and PUT requests to arbitrary hosts specified in the credential configuration, including internal and link-local metadata endpoints.

Impact

An attacker able to influence the credential configuration can cause the application to make unauthorized HTTP requests to internal or external hosts. This can lead to information disclosure or interaction with internal services that are otherwise inaccessible, increasing the attack surface and potentially exposing sensitive data or enabling further attacks.

Summary

The vulnerability in Google::Auth 0.12 arises from the ExternalAccountCredentials::Aws class's retrieve_subject_token method, which sends HTTP requests to URLs specified in the credential_source fields (imdsv2_session_token_url, url, and region_url) without validating the host. This lack of host validation enables SSRF attacks when credentials are built from configurations not fully controlled by the caller, potentially allowing interaction with internal services or metadata endpoints.

CWE-918Server-Side Request Forgery (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
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.
Implementation · Operation
If there is a known list of applications, IP, hostname, and/or domains to which the product is allowed to communicate, then use allowlists to ensure that outgoing requests are restricted to these known entities. The allowlists could be in the application code or possibly enforced by firewalls or network segmentation.
Implementation · Operation
If the product is expected to be able to connect to arbitrary IP addresses or domains, consider using a denylist that includes private network addresses, internal domain names, etc. The denylist could be in the application code or possibly enforced by firewalls or network segmentation.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

metacpan.org/release/CJCOLLIER/Google-Auth-0.12/source/lib/Google/Auth/ExternalAccountCredentials/Aws.pm (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 1 Nov 2026, 17:00 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats