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.
{
"cna_assigner": "GitHub_M",
"cwe_ids": [
"CWE-288"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/53xxx/CVE-2025-53099.json"
}{
"extracted_events": [
{
"cpe": "cpe:2.3:a:sentry:sentry:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "0"
},
{
"fixed": "25.5.0"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "57f0129e1e977b76fe8d16667a586578791a3dcd"
}
],
"source": "REFERENCES_COMMIT"
},
{
"range": [
{
"fixed": "ab5fd932ca6bd46529ba3308b4669e3cee719b8f"
}
],
"source": "REFERENCES_COMMIT"
}
]
}