Sentry: Improper Authentication on SAML SSO process allows user identity linking
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · High · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-287.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| getsentry | sentry | 21.12.0 to before 26.2.0 | 26.2.0 | Patch available | CNA |
| — | sentry (PyPI) | 21.12.0 and later | — | No fix listed | GHSA-ggmg-cqg6-j45g |
- sentry Vendorgetsentry Affected 21.12.0 to before 26.2.0 Fixed in 26.2.0 Patch available CNA
- sentry (PyPI) Vendor— Affected 21.12.0 and later Fixed in — No fix listed GHSA-ggmg-cqg6-j45g
Remediation
- Fix · CNA sentry (getsentry) Fixed in 26.2.0
Timeline
- 2026-10-02 Threatist record created from CVE-2026-27197
- 2026-10-03 Alias added: GHSA-ggmg-cqg6-j45g
- 2026-10-19 EPSS moved to the 50th–90th percentile
- 2026-10-25 EPSS moved to the below the 50th percentile
References
More getsentry vulnerabilities
- TI-2026-21018 Sentry allows unauthorized access to event data across organizational boundaries CVSS 4.0MEDIUM 5.7
- TI-2026-30656 Sentry: Improper authentication on SAML SSO process allows user identity linking CVSS 3.1CRITICAL 9.8
- TI-2026-78982 Sentry-Javascript: Middleware Bypass when using Tunnel route CVSS 4.0CRITICAL 9.1
- TI-2025-16094 Improper authentication on SAML SSO process allows user impersonation in sentry CVSS 3.1CRITICAL 9.1
- TI-2023-25212 Sentry Next.js vulnerable to SSRF via Next.js SDK tunnel endpoint CVSS 3.1CRITICAL 9.3
- TI-2026-37904 Sentry: Inefficient Regular Expression Complexity in sentry CVSS 3.1HIGH 7.5
Sources
- CVE-2026-27197 · CVE Program
- CVE-2026-27197 · NVD
- FIRST EPSS
- GHSA-ggmg-cqg6-j45g · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences