Skip to content
major vulnerability· requires attention

Affects widely used Sentry multi-org deployments; critical auth bypass enabling attacker account takeover.

Applications

CVE-2026-27197

9.1
Critical
EPSS 0.43%Patch availableFeb 21, 2026

Critical Sentry SAML SSO auth bypass enables account takeover.

common questions

Is CVE-2026-27197 being exploited?

Not confirmed. CVE-2026-27197 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.43% probability of exploitation in the next 30 days.

How severe is CVE-2026-27197?

CVE-2026-27197 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-27197?

Yes. A fix has been recorded for CVE-2026-27197. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-27197 affect?

CVE-2026-27197 affects Sentry self-hosted (v21.12.0–v26.1.0), Sentry multi-organization deployments (cloud/self-hosted). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-27197?

Upgrade to 26.2.0+; enforce per-user 2FA.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Sentry self-hosted (v21.12.0–v26.1.0)Sentry multi-organization deployments (cloud/self-hosted)
impact

Account takeover via forged SAML IdP in multi-org Sentry instances; attacker gains victim access.

action required

Patch when possible

affected versions
getsentry sentry
  • affected>= 21.12.0 and < 26.2.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free