SENTRY · CVE-2026-42354 · Package
FIX → 26.4.1
Sentry's SAML SSO code links a user identity without proper authentication when multiple organizations share one instance. An attacker using a malicious SAML identity provider can take over any user account whose email address they know.
first public Apr 22, 2026 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Self-hosted Sentry instances with more than one organization (SENTRY_SINGLE_ORGANIZATION = False) where a user can edit SSO settings for another organization are exposed. Single-organization self-hosted instances and Sentry SaaS need no action per the vendor. Enabling account-based two-factor authentication blocks the takeover path, but organization admins cannot enable it on a user's behalf.
Not affected if managed-hosting, single-organization, sso-not-configured
Who cares multi-organization, saml-sso, self-hosted, sentry
pip show sentry for self-hosted installs.SENTRY_SINGLE_ORGANIZATION is set to False in the self-hosted configuration; only multi-organization instances are exposed.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:
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.
Users can manage their two-factor authentication settings through Account Settings > Security page. For step-by-step details, please see the Sentry helpdesk article.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
Upgrade to 26.4.1
26.4.1 or higher.Please note that this is distinct vulnerability from the similar https://github.com/getsentry/sentry/security/advisories/GHSA-7pq6-v88g-wf3w from 2025.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.