CVE-2026-102899

HIGHPre-NVD 7.67.6
EchelonGraph scoreLOW confidence

This high-severity CVE scores 7.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (28th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: a secondary CVSS source
Trending — 3 sources updated this week
7.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.6Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.6
EG Score
7.6HIGHlow confidence
EG Risk
34
EG Risk 34/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity76% × 45%
The EG Score, 7.6 of 10.
Exploitation0% × 40%
No KEV listing, EG-KEV tier or EPSS when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
28th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 14, 2026

Last Modified

October 15, 2026

Advisory Details (7)

Auto-updated Oct 14, 2026
Patch available. Sources: github_commit, github_pr, github, github_release.
GitHub advisoryMentions a patch (unverified)

Improper authentication on SAML SSO process allows user identity linking · Advisory · getsentry/sentry · GitHub

https://github.com/getsentry/sentry/security/advisories/GHSA-w699-8wff-fqxw
GitHub release Patch Available

26.7.2

Patch available: getsentry/sentry 26.7.2

https://github.com/getsentry/sentry/releases/tag/26.7.2
GitHub pull request

ref(auth): Unify SAML and OAuth identity-confirmation flows on the shared SSO pipeline

Fix merged in getsentry/sentry PR #120702 on 2026-07-27 — awaiting tagged release

https://github.com/getsentry/sentry/pull/120702
GitHub pull request

Ensure SAML assertions called with valid fields

Fix merged in getsentry/sentry PR #120467 on 2026-07-23 — awaiting tagged release

https://github.com/getsentry/sentry/pull/120467
GitHub commit

commit ec963de4ec8c (getsentry/sentry)

Fix landed in getsentry/sentry commit ec963de4ec8c — awaiting tagged release

https://github.com/getsentry/sentry/commit/ec963de4ec8c7f340f286c6f613e55458a9e5ddf
GitHub commit

commit 9c982d4bcb81 (getsentry/sentry)

Fix landed in getsentry/sentry commit 9c982d4bcb81 — awaiting tagged release

https://github.com/getsentry/sentry/commit/9c982d4bcb81c93e2db552084bcbb45cdd34bdd3
GitHub release Patch Available

26.7.2

Patch available: getsentry/self-hosted 26.7.2

https://github.com/getsentry/self-hosted/releases/tag/26.7.2

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 6× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  2. 2026-10-15 15:28 UTCEG score recompute
  3. 2026-10-15 14:40 UTCEG score recompute
  4. 2026-10-14 19:34 UTCEG score recompute
  5. 2026-10-14 19:10 UTCEG score recomputeFirst assessed: 7.6 HIGH
  6. 2026-10-14 19:09 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-102899?
CVE-2026-102899 is a high-severity vulnerability; its CVE record was published on October 14, 2026. 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…
When was the CVE record for CVE-2026-102899 published?
The CVE record for CVE-2026-102899 was published on October 14, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 15, 2026; the record at its source may have been updated since.
Is CVE-2026-102899 actively exploited?
CVE-2026-102899 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (28th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-102899?
CVE-2026-102899 has a CVSS base score of 7.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-102899?
A fix for CVE-2026-102899 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-102899

Explore →

Is Your Infrastructure Affected by CVE-2026-102899?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.