Description
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.
Published: 2026-05-08
Score: 9.1 Critical
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

Sentry’s SAML SSO implementation contains an unauthorized identity linkage flaw (CWE‑290). When an attacker controls a malicious SAML Identity Provider and presents an email address that exists on the target instance, the system accepts the authentication and binds it to the victim’s account. This bypasses normal credential verification, enabling the attacker to assume full control of the user account with all its permissions.

Affected Systems

Sentry installations from version 21.12.0 up to, but not including, 26.4.1 are susceptible. The affected vendor is getsentry:sentry. Attackers must know the target user’s email address and have the ability to configure a rogue SAML provider that the Sentry instance trusts.

Risk and Exploitability

The CVSS score of 9.1 indicates critical severity. No EPSS data is available, but the requirement for a known email address and a malicious SAML provider suggests that remote exploitation is likely available to attackers who can set up such a provider or compromise an existing trusted IdP. The vulnerability is not listed in the CISA KEV catalog, yet the high CVSS and the potential for complete account takeover warrant urgent remediation. The attack vector is inferred to be remote, relying on the SAML SSO trust relationship and knowledge of user emails.

Generated by OpenCVE AI on May 9, 2026 at 00:21 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Sentry to version 26.4.1 or newer, which contains the authorized fix for the SAML authentication flaw.
  • Reconfigure the SAML settings to trust only approved Identity Providers and remove any legacy or unverified IdPs.
  • If SAML SSO functionality is not required, disable it entirely so that the vulnerable code path is not reachable.

Generated by OpenCVE AI on May 9, 2026 at 00:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-rcmw-7mc7-3rj7 Sentry's improper authentication on SAML SSO process allows user identity linking
History

Sat, 09 May 2026 00:45:00 +0000

Type Values Removed Values Added
First Time appeared Getsentry
Getsentry sentry
Vendors & Products Getsentry
Getsentry sentry

Fri, 08 May 2026 23:15:00 +0000

Type Values Removed Values Added
Description 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.
Title Sentry: Improper authentication on SAML SSO process allows user identity linking
Weaknesses CWE-290
References
Metrics cvssV3_1

{'score': 9.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N'}


Subscriptions

Getsentry Sentry
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-05-08T22:58:33.659Z

Reserved: 2026-04-26T13:26:14.515Z

Link: CVE-2026-42354

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-05-08T23:16:38.513

Modified: 2026-05-08T23:16:38.513

Link: CVE-2026-42354

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-05-09T00:30:21Z

Weaknesses