Skip to main content
CVE-2025-53099VulnerabilityPublished

CVE-2025-53099: getsentry sentry · Authentication Bypass Using an Alternate Path or Channel

Affects getsentry sentrySource CVE Database V5

0

Not known to be exploited · CVSS 5.5 Medium : upgrade to 25.5.0 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 25.5.0
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Upgrade getsentry/sentry to 25.5.0.

Affected software

ProductAffectedFixed in
GitHubgetsentry/sentrypkg:github/getsentry/sentryOther threatsAffected
  • <25.5.0
Fixed in
  • 25.5.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations using self-hosted Sentry should immediately upgrade to version 25.5.0 or later to remediate this vulnerability. Beyond patching, organizations should audit all registered OAuth applications for legitimacy and revoke any suspicious or unused apps. Implement strict OAuth app registration policies and monitor OAuth authorization flows for unusual patterns indicative of race condition exploitation. Employ multi-factor authentication (MFA) on user accounts to reduce the risk of token misuse. Network segmentation and access controls should limit the exposure of Sentry instances to only trusted internal networks. Regularly review and rotate OAuth client secrets and tokens to minimize the window of opportunity for attackers. Additionally, implement logging and alerting on OAuth token issuance and de-authorization events to detect anomalies promptly. For organizations with high security requirements, consider deploying runtime application self-protection (RASP) or web application firewalls (WAF) that can detect and block suspicious OAuth flows.

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.

References

Community reviews

Loading reviews…