Skip to content

CVE-2026-27197

Sentry authentication bypass

9.1 CRITICALEPSS 0.58%
  1. Published21 Feb 2026

Description

Sentry 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.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityNone
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected products

Sentry≥ 21.12.0 < 26.2.0

Remediation

Fixed in
Sentry≥ 26.2.0

Frequently asked

Is CVE-2026-27197 being actively exploited?

CVE-2026-27197 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.58%.

How severe is CVE-2026-27197?

CVE-2026-27197 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 0.58% probability of exploitation.

Which products are affected by CVE-2026-27197?

Affected products include Sentry.

How do I fix CVE-2026-27197?

Upgrade affected software to a fixed version, for example Sentry 26.2.0 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-27197 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.