CVE-2025-53099: Sentry Missing Invalidation of Authorization Codes During OAuth Exchange and Revocation
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.
Affected Software
Remediation
Patch Available
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2025-53099?
CVE-2025-53099 has a critical severity rating due to the potential for unauthorized access through flawed OAuth handling.
How do I fix CVE-2025-53099?
To fix CVE-2025-53099, upgrade your Sentry software to version 25.5.0 or later.
Which versions of Sentry are affected by CVE-2025-53099?
CVE-2025-53099 affects all versions of Sentry prior to 25.5.0.
What kind of attack does CVE-2025-53099 exploit?
CVE-2025-53099 can be exploited through a malicious OAuth application exploiting a race condition.
Can I mitigate CVE-2025-53099 without upgrading Sentry?
Mitigation for CVE-2025-53099 is limited, and upgrading to version 25.5.0 or later is the recommended solution.