Sentry Missing Invalidation of Authorization Codes During OAuth Exchange and Revocation
getsentry sentry
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| getsentry sentry |
| No fix yet |
Original 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.
From the CVE record · GitHub_M
References
- github.com/getsentry/sentry/security/advisories/GHSA-mgh8-h4xc-pfmjVendor advisory
- github.com/getsentry/sentry/pull/85570Patch
- github.com/getsentry/sentry/pull/85571Patch
- github.com/getsentry/sentry/pull/86069Issue tracker
- github.com/getsentry/sentry/pull/86532Issue tracker
- github.com/getsentry/sentry/commit/57f0129e1e977b76fe8d16667a586578791a3dcdPatch
- github.com/getsentry/sentry/commit/ab5fd932ca6bd46529ba3308b4669e3cee719b8fPatch
- github.com/getsentry/sentry/commit/e6241254aead969e6c8490a81cde9a01335df19dPatch
- github.com/CVEProject/cvelistV5/tree/main/cves/2025/53xxx/CVE-2025-53099.json
- nvd.nist.gov/vuln/detail/CVE-2025-53099