Google Google::Auth up to 0.12 OAuth State Validation bin/gcloud-auth.pl state state issue

Summaryinfo

A vulnerability has been found in Google Google::Auth up to 0.12 and classified as problematic. The affected element is an unknown function of the file bin/gcloud-auth.pl of the component OAuth State Validation. The manipulation of the argument state leads to state issue. This vulnerability is uniquely identified as CVE-2026-74760. Local access is required to approach this attack. No exploit exists.

Detailsinfo

A vulnerability was found in Google Google::Auth up to 0.12. It has been rated as problematic. This issue affects an unknown part of the file bin/gcloud-auth.pl of the component OAuth State Validation. The manipulation of the argument state with an unknown input leads to a state issue vulnerability. Using CWE to declare the problem leads to CWE-371. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Google::Auth versions from 0.11 through 0.12 for Perl accept an authorization code from any local process because the gcloud-auth login callback does not check the OAuth state. The gcloud-auth login and application-default login commands send a state parameter with the authorization request, then take the code from the first request to reach their loopback listener without comparing the returned state. A local attacker can submit an authorization code for their own Google account. The CLI exchanges it and stores the refresh token as the user's credentials, so the user's tools then act as the attacker's account.

The advisory is shared at metacpan.org. The identification of this vulnerability is CVE-2026-74760 since 08/15/2026. The exploitation is known to be easy. An attack has to be approached locally. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 11/01/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Programming Language Software

Vendor

• Google

Name

• Google::Auth

Version

• 0.1
• 0.2
• 0.3
• 0.4
• 0.5
• 0.6
• 0.7
• 0.8
• 0.9
• 0.10
• 0.11
• 0.12

License

• free

Website

• Vendor: https://www.google.com/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion