CVE-2026-27197
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSentry is a developer-first error tracking and performance monitoring tool. Versions 21.12.0 through 26.1.0 have a critical vulnerability in its SAML SSO implementation which allows an attacker to take over any user account by using a malicious SAML Identity Provider and another organization on the same Sentry instance. Self-hosted users are only at risk if the following criteria is met: ore than one organizations are configured (SENTRY_SINGLE_ORGANIZATION = True), or malicious user has existing access and permissions to modify SSO settings for another organization in a multo-organization instance. This issue has been fixed in version 26.2.0. To workaround this issue, implement user account-based two-factor authentication to prevent 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSentry versions 21.12.0-26.1.0 contain a critical SAML SSO vulnerability allowing account takeover via a malicious Identity Provider. The flaw exploits the multi-organization architecture, enabling an attacker to hijack any user account when multiple organizations exist on a single Sentry instance or when SENTRY_SINGLE_ORGANIZATION is enabled.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 21.12.0, < 26.2.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Sentry versionCheck your Sentry installation's version by querying the Python package (pip show sentry) or checking the UI footer in the web interface. Compare this version number against the affected range: >= 21.12.0 and < 26.2.0Affected if The installed version falls within 21.12.0 through 26.1.x (any version before 26.2.0)
-
Verify multi-organization architectureQuery your Sentry database or use the CLI (sentry organizations list) to determine how many organizations exist on this Sentry instance. Alternatively, check the SENTRY_ORGANIZATION setting in your config file if present.Affected if More than one organization exists on the Sentry instance, or SENTRY_SINGLE_ORGANIZATION is not set to true (defaults to multi-tenant)
-
Confirm SAML SSO is the authentication methodReview your Sentry authentication settings in the UI under Organization Settings > Auth, or inspect your configuration files for SAML provider configuration (such as Okta, Azure AD, or other IdP integrations).Affected if SAML-based SSO authentication is enabled and configured for any organization on this instance
A Sentry instance is affected if it runs version 21.12.0 through 26.1.x, uses SAML authentication, and operates in multi-organization mode (multiple orgs present or SENTRY_SINGLE_ORGANIZATION not explicitly set to true).
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped26.2.0
Primary fix: upgrade to Sentry 26.2.0. Workaround: enforce user-based two-factor authentication to prevent authentication completion by attackers.
26.2.0
- Upgrade Sentry to version 26.2.0 or later to address the SAML SSO authentication bypass vulnerability
- After upgrading, verify the SAML SSO configuration is intact and functioning properly
- Review all organization SSO settings to ensure no unauthorized changes were made
- As an additional security measure, encourage all users to enable two-factor authentication on their accounts
- If unable to upgrade immediately, ensure SENTRY_SINGLE_ORGANIZATION is not set to True in multi-organization instances and audit user permissions for SSO configuration access
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27197 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-27197 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data