Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
CRITICAL severity

CVE-2020-7692 — google-oauth-client

CRITICALFix: googleapis/google-oauth-java-client@13433cd

CVE-2020-7692 is a critical-severity (CVSS 9.1) CWE-863 vulnerability in com.google.oauth-client:google-oauth-client. 2 public exploit references exist, so weaponization risk is real. A fix is available for com.google.oauth-client:google-oauth-client — see the affected versions and patch details below.

Improper Authorization in Google OAuth Client

Also known asGHSA-f263-c949-w85gSNYK-JAVA-COMGOOGLEOAUTHCLIENT-575276
Published
Jul 9, 2020
Updated
Jul 9, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
2 known
Exploitation data as of Sep 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs75th percentile — riskier than 75% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

CVE-2020-7692 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

1 pkg affected
☕com.google.oauth-client:google-oauth-client

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

PKCE support is not implemented in accordance with the RFC for OAuth 2.0 for Native Apps. Without the use of PKCE, the authorization code returned by an authorization server is not enough to guarantee that the client that issued the initial authorization request is the one that will be authorized. An attacker is able to obtain the authorization code using a malicious app on the client-side and use it to gain authorization to the protected resource. This affects the package com.google.oauth-client:google-oauth-client before 1.31.0.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavencom.google.oauth-client:google-oauth-clientall versions1.31.0com.google.oauth-client:google-oauth-client:1.31.0
Exploits & PoCs
2

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.google.oauth-client:google-oauth-client, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update com.google.oauth-client:google-oauth-client to 1.31.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-7692 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2020-7692 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2020-7692. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant
ProductFixed inAdvisory
OCP-Tools-4.12-RHEL-8jenkins-2-plugins-0:4.12.1698294000-1.el8RHSA-2023:6172
OCP-Tools-4.12-RHEL-8jenkins-2-plugins-0:4.12.1706515741-1.el8RHSA-2024:0778
OCP-Tools-4.13-RHEL-8jenkins-2-plugins-0:4.13.1684911916-1.el8RHSA-2023:3299
Red Hat OpenShift Container Platform 4.10jenkins-2-plugins-0:4.10.1675144701-1.el8RHSA-2023:0560
Red Hat OpenShift Container Platform 4.9jenkins-2-plugins-0:4.9.1675668922-1.el8RHSA-2023:0777

Frequently Asked Questions

PKCE support is not implemented in accordance with the RFC for OAuth 2.0 for Native Apps. Without the use of PKCE, the authorization code returned by an authorization server is not enough to guarantee that the client that issued the initial authorization request is the one that will be authorized. An attacker is able to obtain the authorization code using a malicious app on the client-side and use it to gain authorization to the protected resource. This affects the package com.google.oauth-client:google-oauth-client before 1.31.0.
O3 Security · Impact-Aware SCA

Is CVE-2020-7692 in your dependencies?

O3 Security finds CVE-2020-7692 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

CVE-2020-7692: google-oauth (Critical 9.1) | O3 Security