Sentry is an application monitoring and error tracking platform. From 26.5.0 until 26.7.2, the SAML SSO identity-linking flow allows an attacker who controls a SAML identity provider to socially engineer an authenticated user into opening a malicious URL, link the attacker's identity to the victim's Sentry account, and take control of that account. The attack requires a browser that accepts the cross-site cookie context, including Firefox with SameSite=None cookies or Chromium with third-party cookies enabled. Sentry SaaS received the remediation on July 27, 2026, and self-hosted Sentry is fixed in version 26.7.2.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 2
- StatusReceived → Awaiting AnalysisNVD modified 2026-10-16 16:00
- First seenCVSS 7.6NVD modified 2026-10-14 19:17
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 7
- https://github.com/getsentry/self-hosted/releases/tag/26.7.2
- https://github.com/getsentry/sentry/commit/9c982d4bcb81c93e2db552084bcbb45cdd34bdd3
- https://github.com/getsentry/sentry/commit/ec963de4ec8c7f340f286c6f613e55458a9e5ddf
- https://github.com/getsentry/sentry/pull/120467
- https://github.com/getsentry/sentry/pull/120702
- https://github.com/getsentry/sentry/releases/tag/26.7.2
- https://github.com/getsentry/sentry/security/advisories/GHSA-w699-8wff-fqxw