# CVE-2026-102899: Sentry: Improper authentication on SAML SSO process allows user identity linking

> Attackers can link their identity to victim accounts via SAML SSO, leading to account takeover, requiring specific browser cookie settings.

- **Severity:** High 7.6 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-w699-8wff-fqxw

## What is CVE-2026-102899?

CVE-2026-102899 is a high-severity authentication bypass vulnerability in getsentry sentry, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-102899?


## How do I fix CVE-2026-102899?

No fix has been published for CVE-2026-102899 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-102899 being exploited?

There is no known exploitation of CVE-2026-102899 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-102899 and fix it if it is affected.

What it is: CVE-2026-102899 is a high-severity authentication bypass vulnerability in getsentry sentry, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-102899 in the wild and no public exploit code.

Affected product: getsentry sentry. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-102899/ (Markdown: https://insights.sbomify.com/CVE-2026-102899/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-102899
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-102899
- OSV: https://osv.dev/vulnerability/CVE-2026-102899

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-102899/
Summaries are generated and may contain mistakes; the official description above is the record.