CVE-2026-42354: Sentry's improper authentication on SAML SSO process allows user identity linking
A critical vulnerability was discovered in the SAML SSO implementation of Sentry. It was reported to us via Sentry’s private bug bounty program.
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.
Self-hosted users are only vulnerable if the following conditions are met:
- They have more than one organization configured (SENTRY_SINGLE_ORGANIZATION = False).
- A malicious user has existing access and permissions to modify SSO settings for another organization in their multi-organization instance.
References
- github.com/advisories/GHSA-rcmw-7mc7-3rj7
- github.com/getsentry/sentry
- github.com/getsentry/sentry/commit/0c67558ae7fe08738912d4c5233b53ead048da3b
- github.com/getsentry/sentry/pull/113720
- github.com/getsentry/sentry/releases/tag/26.4.1
- github.com/getsentry/sentry/security/advisories/GHSA-rcmw-7mc7-3rj7
- nvd.nist.gov/vuln/detail/CVE-2026-42354
Code Behaviors & Features
Detect and mitigate CVE-2026-42354 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →