High severity · published Jul 1, 2025
CVE-2025-53099
Sentry Missing Invalidation of Authorization Codes During OAuth Exchange and Revocation
7.5
CVSS
0.8%
EPSS
No
On KEV
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.
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Confidentiality
High
Integrity
High
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.8% · higher than 56% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
SE
sentry · getsentry
< 25.5.0 · source: vendor, NVD
Affected product
SE
sentry
getsentry
More from sentry
9.8
CVE-2026-42354
Sentry: Improper authentication on SAML SSO process allows user identity linking
9.1
CVE-2026-27197
Sentry: Improper Authentication on SAML SSO process allows user identity linking
9.1
CVE-2025-22146
Improper authentication on SAML SSO process allows user impersonation in sentry
8.1
CVE-2023-39349
Sentry vulnerable to privilege escalation via ApiTokensEndpoint
7.7
CVE-2026-83803
Sentry: Unsafe pickle deserialization in Relocation Feature