Servers and applications
GHSA-rrcx-889m-5jj5
Improper authentication on SAML SSO allows unauthorized organization member addition or identity linking
- Severity
- Critical
- Published
- 17 Aug 2026
- Last changed
- 17 Aug 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 20.6.0
- Sources
- Project advisories (GitHub)
Description
A critical vulnerability was discovered in the SAML SSO implementation of Sentry. This issue was reported to us via our private bug bounty program.
The vulnerability allows an attacker to take control of any authenticated Sentry user account by using an attacker-controlled SAML Identity Provider using a known ident value and an organization slug. This same vulnerability may allow an attacker to add themselves as an unauthorized organization member under the organization's default user role.
For SaaS users, you are only vulnerable if the additional conditions are met:
- You have SAML SSO authentication configured
For self-hosted users, you are only vulnerable if the additional conditions are met:
- You 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 your multi-organization instance.
Workarounds
There is no workaround available for the unauthorized organization member addition.
User account-based two-factor authentication prevents an attacker from being able to complete authentication with a victim's user account. Organization administrators cannot do this on a user's behalf, this requires individual users to ensure 2FA has been enabled for their account.
You can manage your two-factor authentication settings on your Account Settings > Security page. For step-by-step details, please see our helpdesk article.
Affected software
| Software | Affected versions |
|---|---|
SentryServers and applications · github:getsentry/sentry |
|
About Sentry
Developer-first error tracking and performance monitoring
- Weekly downloads (PyPI)
- 720PyPI Stats, 15 Nov 2026
- Docker Hub pulls
- 241,950,123Docker Hub, 15 Nov 2026
- GitHub stars
- 45,780GitHub, 15 Nov 2026
- Forks
- 4,977GitHub, 15 Nov 2026
- Latest release
- 26.10.1GitHub, 15 Nov 2026
- Released
- 28 Oct 2026GitHub
- First published on GitHub
- 30 Aug 2010GitHub
Source code Website Docker image Package
Vulnerabilities in Sentry
- In our list
- 24
- Published in the last 12 months
- 10
- Critical, last 12 months
- 4
- High, last 12 months
- 4
- Known exploited
- 0
- GHSA-88p9-44cg-fr2qImproper email matching in SAML SSO process allows account takeoverHigh 8.1 19 Oct 2026
- CVE-2026-102899Improper authentication on SAML SSO process allows user identity linkingHigh 7.6 24 Jul 2026
- CVE-2026-83803Unsafe pickle deserialization in Relocation FeatureCritical 16 Jul 2026
- GHSA-fx76-375g-xq25Attempts at prompt injection and supply chain compromise with public Data Source Names (DSNs)Low 5 Jun 2026
- CVE-2026-52794Inefficient Regular Expression Complexity in SentryHigh 7.5 3 Jun 2026
- CVE-2021-47935Sentry 8.2.0 contains a remote code execution vulnerability that allows authenticated superusers to execute arbitrary commands by injecting malicious pickle-serialized objects through the audit log entry data parameter. Attackers can submit crafted POST requests to the admin audit log endpoint with base64-encoded compressed pickle payloads in the data field to achieve code execution with…High 8.7 10 May 2026
References
- GitHub Advisory Database https://github.com/advisories/GHSA-rrcx-889m-5jj5
- github.com https://github.com/getsentry/sentry/security/advisories/GHSA-rrcx-889m-5jj5