{"id":"CVE-2025-53099","aliases":["EUVD-2025-19628","GHSA-mgh8-h4xc-pfmj"],"status":"published","title":"Sentry Missing Invalidation of Authorization Codes During OAuth Exchange and Revocation","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.","severity":{"version":"4.0","score":5.5,"vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-12","score":0.00798,"percentile":0.56998,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":false},"cwes":["CWE-288"],"published":"2025-07-01T14:53:16Z","modified":"2026-10-28T02:30:58Z","products":[{"vendor":"getsentry","product":"sentry"},{"vendor":"sentry","product":"sentry"}],"references":[{"url":"https://github.com/getsentry/sentry/security/advisories/GHSA-mgh8-h4xc-pfmj","tags":["x_refsource_CONFIRM","Vendor Advisory","advisory"]},{"url":"https://github.com/getsentry/sentry/pull/85570","tags":["x_refsource_MISC","Issue Tracking","Patch","fix"]},{"url":"https://github.com/getsentry/sentry/pull/85571","tags":["x_refsource_MISC","Issue Tracking","Patch","fix"]},{"url":"https://github.com/getsentry/sentry/pull/86069","tags":["x_refsource_MISC","Issue Tracking","fix"]},{"url":"https://github.com/getsentry/sentry/pull/86532","tags":["x_refsource_MISC","Issue Tracking","fix"]},{"url":"https://github.com/getsentry/sentry/commit/57f0129e1e977b76fe8d16667a586578791a3dcd","tags":["x_refsource_MISC","Patch","fix"]},{"url":"https://github.com/getsentry/sentry/commit/ab5fd932ca6bd46529ba3308b4669e3cee719b8f","tags":["x_refsource_MISC","Patch","fix"]},{"url":"https://github.com/getsentry/sentry/commit/e6241254aead969e6c8490a81cde9a01335df19d","tags":["x_refsource_MISC","Patch","fix"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/53xxx/CVE-2025-53099.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-53099","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2025-53099","title":"Sentry Missing Invalidation of Authorization Codes During OAuth Exchange and Revocation","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.","status":"published","published":"2025-07-01T14:53:16.878Z","modified":"2025-07-01T15:06:29.774Z","cvss":[{"version":"4.0","score":5.5,"vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H","level":"medium","assessor":"cna"}],"cwes":["CWE-288"],"updated_at":"2026-11-02T14:32:49.180768Z"}],"euvd":[{"id":"EUVD-2025-19628","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.","status":"published","published":"2025-07-01T14:53:16Z","modified":"2025-07-01T15:06:29Z","cvss":[{"version":"4.0","score":5.5,"vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H","level":"medium"}],"updated_at":"2026-11-02T20:32:14.813568Z"}],"nvd":[{"id":"CVE-2025-53099","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.","status":"published","published":"2025-07-01T15:15:26.277Z","modified":"2026-06-17T09:37:37.383Z","cvss":[{"version":"4.0","score":5.5,"vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"medium","assessor":"secondary"},{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"primary"}],"cwes":["CWE-288"],"updated_at":"2026-11-02T14:11:15.754475Z"}],"osv":[{"id":"CVE-2025-53099","title":"Sentry Missing Invalidation of Authorization Codes During OAuth Exchange and Revocation","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.","status":"published","published":"2025-07-01T14:53:16.878Z","modified":"2026-10-28T02:30:58.620420602Z","cvss":[{"version":"4.0","score":5.5,"vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H","level":"medium"}],"cwes":["CWE-288"],"updated_at":"2026-11-02T15:44:50.45326Z"}]}}