# CVE-2026-102899: Sentry SAML SSO identity-linking account takeover

Source: https://junglewise.ai/threats/cve-2026-102899-sentry-is-an-application-monitoring-and-error-tracking-platform  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-14. Updated: 2026-10-16  
License: CC BY 4.0 with a link back

CVE-2026-102899 · Severity: info · Published 2026-10-14

Sentry is an application monitoring platform that enterprises use to track errors and performance issues. A flaw in its SAML single sign-on feature allows an attacker who controls a SAML identity provider to trick an authenticated user into opening a malicious link, then hijack the user's Sentry account and access all their monitoring data and projects. The attack works only in browsers configured to accept cross-site cookies.

Technologies: [Sentry](https://junglewise.ai/threats/technologies/sentry-sentry). Vendors: [Sentry](https://junglewise.ai/threats/vendors/sentry).

## Quick answers

**Is CVE-2026-102899 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-102899 being exploited in the wild.

**How severe is CVE-2026-102899?** Informational severity, published 14 October 2026.

**Which products and versions are affected?** Sentry 26.5.0 to 26.7.1.

**Is there a fix for CVE-2026-102899?** Yes: fixed in 26.7.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-102899 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-102899?** Check whether you run Sentry at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 26.7.2

## Technical details

The SAML SSO identity-linking flow improperly validates the confirmation step for linking external identities to user accounts, allowing an attacker to submit identity-linking requests on behalf of a victim user in the cross-site cookie context. An authenticated user must be socially engineered into clicking a malicious URL, but the lack of CSRF protections or secure confirmation flow allows the attacker's identity to be linked to the victim's account. The fix (version 26.7.2) unifies SAML and OAuth confirmation flows through a shared SSO pipeline with proper state validation.

## Affected products

- Sentry Sentry 26.5.0 to 26.7.1

## Timeline

- 2026-10-14: disclosed
- 2026-07-27: patched: Sentry SaaS remediated
- 2026-07-28: patched: Self-hosted version 26.7.2 released

## References

- [https://github.com/getsentry/self-hosted/releases/tag/26.7.2](https://github.com/getsentry/self-hosted/releases/tag/26.7.2)
- [https://github.com/getsentry/sentry/commit/9c982d4bcb81c93e2db552084bcbb45cdd34bdd3](https://github.com/getsentry/sentry/commit/9c982d4bcb81c93e2db552084bcbb45cdd34bdd3)

## Related threats

- [Sentry unsafe deserialization in relocation import](https://junglewise.ai/threats/cve-2026-83803-sentry-is-an-error-tracking-and-performance-monitoring-tool-from)