Advisory record · GHSA-f263-c949-w85g

Improper Authorization in Google OAuth Client

CVSS 7.4 HighEPSS 0.015 · 75th percentile

Published by the GitHub Advisory Database at 28 Sept 2021, 16:16 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
com.google.oauth-client:google-oauth-clientMaven<1.31.01.31.0
Identifiers
GHSA-f263-c949-w85g · CVE-2020-7692 · SNYK-JAVA-COMGOOGLEOAUTHCLIENT-575276
Weakness (CWE)
CWE-862 · CWE-863
Published
28 Sept 2021
Updated
8 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The com.google.oauth-client:google-oauth-client package is vulnerable in versions before 1.31.0. Its PKCE support does not follow the RFC for OAuth 2.0 for Native Apps, so an authorization code is not enough to confirm that the client receiving it is the one that started the request. An attacker with a malicious app on the client side can obtain the code and use it to gain access to protected resources. Upgrade to version 1.31.0 or later.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.4 High 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N CNA (snyk)
  • CISA KEV Not listed.
  • EPSS 0.015, the 75th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:19 UTC First seen by agentprime
  2. 31 Oct 2026, 14:19 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.