Threats affecting pkg:github/getsentry/sentry

A vulnerability in Sentry versions 26.5.0 through 26.7.1 allows an attacker controlling a SAML identity provider to link their identity to a victim's Sentry account via a socially engineered malicious URL. This improper authentication issue requires a browser that accepts cross-site cookie contexts, such as Firefox with SameSite=None cookies or Chromium with third-party cookies enabled. The vulnerability is fixed in version 26.7.2 and was remediated in the Sentry SaaS environment on July 27, 2026.

Sentry is an error tracking and performance monitoring tool. From 23.11.0 until 26.7.0, Sentry instances with the relocation feature enabled unsafely deserialize a legacy database field while importing a user-supplied relocation archive. An authenticated user can craft an archive that causes arbitrary code execution in the import worker process. Self-hosted installations using the default configuration are not affected because the relocation feature is disabled by default. This issue is fixed in version 26.7.0.

Sentry is an error tracking and performance monitoring tool. From 24.4.0 until 26.5.2, a Regular Expression Denial of Service (ReDoS) vulnerability exists in Sentry's event ingestion pipeline, where a regex applied to attacker-controlled fields on incoming events can be made to consume disproportionate CPU time. This vulnerability is fixed in 26.5.2.

Sentry is an error tracking and performance monitoring tool. From version 21.12.0 to before version 26.4.1, a critical vulnerability was discovered in the SAML SSO implementation of Sentry. The vulnerability allows an attacker to take over any user account by using a malicious SAML Identity Provider and another organization on the same Sentry instance. The victim email address must be known in order to exploit this vulnerability. This issue has been patched in version 26.4.1.

CVE-2026-26004 is an authorization bypass vulnerability in getsentry's Sentry product affecting versions prior to 26.1.0. It involves an Insecure Direct Object Reference (IDOR) in the GroupEventJsonView endpoint, allowing users with limited privileges to access data across organizations. The vulnerability does not require user interaction or authentication beyond low privileges, making exploitation feasible in network environments. The flaw was patched in version 26.1.0. The CVSS 4.0 score is 5.

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.