CVE-2026-42354: Sentry's improper authentication on SAML SSO process allows user identity linking
Affects sentrySource GCVE Database
Not known to be exploited · CVSS 9.1 Critical : upgrade to 26.4.1 as a priority.
Data as of 16 Nov 2026, 17:50 UTC
- Patch
- Available – fixed in 26.4.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 8 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 15 Nov 2026.
What to do
Upgrade sentry to 26.4.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PyPIsentry | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
For Sentry SaaS users, the fix has been deployed and no action is required. Self-hosted users should upgrade to version 26.4.1 or higher unless they have a single organization configured (SENTRY_SINGLE_ORGANIZATION = True), in which case no action is needed. Enabling user account-based two-factor authentication (2FA) is strongly recommended as it prevents attackers from completing authentication even if they exploit this vulnerability. Users must enable 2FA individually; organization administrators cannot enable it on their behalf.
Description
A critical vulnerability in Sentry's SAML SSO implementation allows an attacker to take over any user account by using a malicious SAML Identity Provider and another organization on the same Sentry instance. Exploitation requires knowledge of the victim's email address. Self-hosted users are vulnerable only if multiple organizations are configured and a malicious user can modify SSO settings in another organization. The vulnerability is fixed in version 26.4.1. Two-factor authentication (2FA) can mitigate the risk by preventing attackers from completing authentication.
References
- github.com/getsentry/sentry/security/advisories/GHSA-rcmw-7mc7-3rj7 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-42354 (opens in a new tab)
- github.com/getsentry/sentry/pull/113720 (opens in a new tab)
- github.com/getsentry/sentry/commit/0c67558ae7fe08738912d4c5233b53ead048da3b (opens in a new tab)
- github.com/getsentry/sentry (opens in a new tab)
- github.com/getsentry/sentry/releases/tag/26.4.1 (opens in a new tab)
- github.com/pypa/advisory-database/tree/main/vulns/sentry/PYSEC-2026-534.yaml (opens in a new tab)
- pypi.org/project/sentry (opens in a new tab)