Sentry Missing Invalidation of Authorization Codes During OAuth Exchange and Revocation
Vulnerability 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.
Impact Analysis
Refer to official advisory for detailed impact metrics.
Remediation
Ensure systems are updated to the latest vendor-supplied patch levels.
Am I Vulnerable?
Launch our assessment wizard to check if your infrastructure is exposed to • CVE-2025-53099
Credits & Attribution
No credits recorded in the NVD database.
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
More from getsentry
View All →Affected Vendor
getsentry
View all reports →