Impact
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.
Patches
- Sentry SaaS: The fix was deployed on August 7, 2026. No action is required.
- Self-Hosted Sentry: If only a single organization is allowed (SENTRY_SINGLE_ORGANIZATION = True), then no action is needed. We recommend upgrading to version 26.8.0 or higher.
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.
References
Muhammad-Qasim-Munir Reporter
Impact
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
identvalue 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:
For self-hosted users, you are only vulnerable if the additional conditions are met:
Patches
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.
References