{"uuid": "719f51e7-b116-4a9e-b7c3-a41b93ec0c8c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-53099", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/20042", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-53099\n\ud83d\udd25 CVSS Score: 5.5 (cvssV4_0, 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)\n\ud83d\udd39 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.\n\ud83d\udccf Published: 2025-07-01T14:53:16.878Z\n\ud83d\udccf Modified: 2025-07-01T14:53:16.878Z\n\ud83d\udd17 References:\n1. https://github.com/getsentry/sentry/security/advisories/GHSA-mgh8-h4xc-pfmj\n2. https://github.com/getsentry/sentry/pull/85570\n3. https://github.com/getsentry/sentry/pull/85571\n4. https://github.com/getsentry/sentry/pull/86069\n5. https://github.com/getsentry/sentry/pull/86532\n6. https://github.com/getsentry/sentry/commit/57f0129e1e977b76fe8d16667a586578791a3dcd\n7. https://github.com/getsentry/sentry/commit/ab5fd932ca6bd46529ba3308b4669e3cee719b8f\n8. https://github.com/getsentry/sentry/commit/e6241254aead969e6c8490a81cde9a01335df19d", "creation_timestamp": "2025-07-01T15:07:56.000000Z"}