Home

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.

PUBLISHED Reserved 2025-06-25 | Published 2025-07-01 | Updated 2025-07-01 | Assigner GitHub_M




MEDIUM: 5.5CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H

Problem types

CWE-288: Authentication Bypass Using an Alternate Path or Channel

Product status

< 25.5.0
affected

References

github.com/...sentry/security/advisories/GHSA-mgh8-h4xc-pfmj

github.com/getsentry/sentry/pull/85570

github.com/getsentry/sentry/pull/85571

github.com/getsentry/sentry/pull/86069

github.com/getsentry/sentry/pull/86532

github.com/...ommit/57f0129e1e977b76fe8d16667a586578791a3dcd

github.com/...ommit/ab5fd932ca6bd46529ba3308b4669e3cee719b8f

github.com/...ommit/e6241254aead969e6c8490a81cde9a01335df19d

cve.org (CVE-2025-53099)

nvd.nist.gov (CVE-2025-53099)

Download JSON