Sentry Missing Invalidation of Authorization Codes During OAuth Exchange and Revocation
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| getsentry | sentry | affected |
|
No data.
| Vendor | Product | Versions |
|---|---|---|
| Getsentry | Sentry | — |
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-19628 | 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. |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.798% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Sentry
Sentry sentry |
|
| CPEs | cpe:2.3:a:sentry:sentry:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Sentry
Sentry sentry |
|
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Sentry Missing Invalidation of Authorization Codes During OAuth Exchange and Revocation | |
| Weaknesses | CWE-288 | |
| References |
|
|
| Metrics |
cvssV4_0
|