CVE-2026-42354 json
Sentry: Improper authentication on SAML SSO process allows user identity linking
published 6mo ago modified 3mo ago also EUVD-2026-28860 , GHSA-rcmw-7mc7-3rj7 , PYSEC-2026-534
- cvss
- 9.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 50%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- pypi sentry 26.4.1
- sentry sentry 26.4.1
- github.com/getsentry/sentry@0c67558 commit
- github.com/getsentry/sentry#113720 pull request
- github.com/getsentry/sentry/releases/tag/26.4.1 release
Is CVE-2026-42354 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 5mo ago
Exploit prediction
0.62% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
| GitHub | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| OSV | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | sentry | >=21.12.0, <26.4.1 |
26.4.1 |
Affected products
- getsentry sentry
Classification
- Weakness
-
- CWE-290 Authentication Bypass by Spoofing
References
-
github.com
/getsentry/sentry/pull/113720
web, issue-tracking, patch
-
github.com
/getsentry/sentry/commit/0c67558ae7fe08738912d4c5233b53ead048da3b
web, patch
-
github.com
/getsentry/sentry/security/advisories/GHSA-rcmw-7mc7-3rj7
web, mitigation, vendor-advisory
-
github.com
/getsentry/sentry/releases/tag/26.4.1
web, product, release-notes
-
nvd.nist.gov
/vuln/detail/CVE-2026-42354
advisory
-
github.com
/getsentry/sentry
package
-
pypi.org
/project/sentry
package
-
github.com
/advisories/GHSA-rcmw-7mc7-3rj7
advisory
Sources
- CVE List CVE-2026-42354
- GitHub Advisory GHSA-rcmw-7mc7-3rj7
- NVD CVE-2026-42354
- OSV PYSEC-2026-534
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.