CVE-2026-27197

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-04-17. A secondary CVSS source baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-7736 (ENISA EUVD) · GHSA-ggmg-cqg6-j45g (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
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.5%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
41
EG Risk 41/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability 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.5%
EPSS %ILE
42nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-02). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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.

The score's inputs: 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

February 21, 2026

Last Modified

June 17, 2026

Advisory Details (1)

Auto-updated Sep 16, 2026
Patch available. Sources: github.
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-ggmg-cqg6-j45g

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipsentry—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
sentry21.12.0 ... 23.7.1 (27 versions)
  • 21.12.0 on: no fix on record
  • 21.12.0 up to 26.2.0: fixed in 26.2.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 21× in last 7d / 77× 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.

Showing the most recent 97 of 164 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 100 are merged into the row they repeat. The 67 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 20:43 UTCEG score recompute
  2. 2026-11-02 20:43 UTCGHSA enrichmentGHSA-ggmg-cqg6-j45g · GitHub severity CRITICAL · GitHub CVSS 9.1
  3. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  4. 2026-11-01 20:07 UTCEG score recompute
  5. 2026-11-01 20:07 UTCGHSA enrichmentGHSA-ggmg-cqg6-j45g · GitHub severity CRITICAL · GitHub CVSS 9.1
  6. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  7. 2026-10-31 19:32 UTCEG score recompute
  8. 2026-10-31 19:32 UTCGHSA enrichmentGHSA-ggmg-cqg6-j45g · GitHub severity CRITICAL · GitHub CVSS 9.1
  9. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  10. 2026-10-30 18:57 UTCEG score recompute
  11. 2026-10-30 18:57 UTCGHSA enrichmentGHSA-ggmg-cqg6-j45g · GitHub severity CRITICAL · GitHub CVSS 9.1
  12. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  13. 2026-10-29 18:22 UTCEG score recompute
  14. 2026-10-29 18:22 UTCGHSA enrichmentGHSA-ggmg-cqg6-j45g · GitHub severity CRITICAL · GitHub CVSS 9.1
  15. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  16. 2026-10-28 17:47 UTCEG score recompute
  17. 2026-10-28 17:47 UTCGHSA enrichmentGHSA-ggmg-cqg6-j45g · GitHub severity CRITICAL · GitHub CVSS 9.1
  18. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  19. 2026-10-27 17:11 UTCEG score recompute
  20. 2026-10-27 17:11 UTCGHSA enrichmentGHSA-ggmg-cqg6-j45g · GitHub severity CRITICAL · GitHub CVSS 9.1
  21. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  22. 2026-10-26 16:34 UTCEG score recompute
  23. 2026-10-26 16:33 UTCGHSA enrichmentGHSA-ggmg-cqg6-j45g · GitHub severity CRITICAL · GitHub CVSS 9.1
  24. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  25. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
Show 72 more
  1. 2026-10-25 15:45 UTCGHSA enrichmentGHSA-ggmg-cqg6-j45g · GitHub severity CRITICAL · GitHub CVSS 9.1
  2. 2026-10-25 14:39 UTCEG score recompute
  3. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  4. 2026-10-24 15:08 UTCEG score recompute
  5. 2026-10-24 15:08 UTCGHSA enrichmentGHSA-ggmg-cqg6-j45g · GitHub severity CRITICAL · GitHub CVSS 9.1
  6. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  7. 2026-10-23 14:33 UTCEG score recompute
  8. 2026-10-23 14:32 UTCGHSA enrichmentGHSA-ggmg-cqg6-j45g · GitHub severity CRITICAL · GitHub CVSS 9.1
  9. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  10. 2026-10-22 13:54 UTCEG score recompute
  11. 2026-10-22 13:54 UTCGHSA enrichmentGHSA-ggmg-cqg6-j45g · GitHub severity CRITICAL · GitHub CVSS 9.1
  12. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  13. 2026-10-21 13:18 UTCEG score recompute
  14. 2026-10-21 13:18 UTCGHSA enrichmentGHSA-ggmg-cqg6-j45g · GitHub severity CRITICAL · GitHub CVSS 9.1
  15. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  16. 2026-10-20 12:27 UTCEG score recompute
  17. 2026-10-20 12:27 UTCGHSA enrichmentGHSA-ggmg-cqg6-j45g · GitHub severity CRITICAL · GitHub CVSS 9.1
  18. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  19. 2026-10-19 11:49 UTCEG score recompute
  20. 2026-10-19 11:48 UTCGHSA enrichmentGHSA-ggmg-cqg6-j45g · GitHub severity CRITICAL · GitHub CVSS 9.1
  21. 2026-10-18 09:49 UTCGHSA enrichmentGHSA-ggmg-cqg6-j45g · GitHub severity CRITICAL · GitHub CVSS 9.1
  22. 2026-10-18 03:51 UTCEG score recompute
  23. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  24. 2026-10-17 08:24 UTCEG score recompute
  25. 2026-10-17 08:24 UTCGHSA enrichmentGHSA-ggmg-cqg6-j45g · GitHub severity CRITICAL · GitHub CVSS 9.1
  26. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  27. 2026-10-16 07:47 UTCEG score recompute
  28. 2026-10-16 07:47 UTCGHSA enrichmentGHSA-ggmg-cqg6-j45g · GitHub severity CRITICAL · GitHub CVSS 9.1
  29. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  30. 2026-10-15 06:47 UTCEG score recompute
  31. 2026-10-15 06:47 UTCGHSA enrichmentGHSA-ggmg-cqg6-j45g · GitHub severity CRITICAL · GitHub CVSS 9.1
  32. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  33. 2026-10-14 02:31 UTCEG score recompute
  34. 2026-10-14 02:30 UTCGHSA enrichmentGHSA-ggmg-cqg6-j45g · GitHub severity CRITICAL · GitHub CVSS 9.1
  35. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  36. 2026-10-12 22:45 UTCEG score recompute
  37. 2026-10-12 22:45 UTCGHSA enrichmentGHSA-ggmg-cqg6-j45g · GitHub severity CRITICAL · GitHub CVSS 9.1
  38. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  39. 2026-10-12 16:17 UTCEG score recompute
  40. 2026-10-12 08:53 UTCGHSA enrichmentGHSA-ggmg-cqg6-j45g · GitHub severity CRITICAL · GitHub CVSS 9.1
  41. 2026-10-11 20:00 UTCEG score recompute
  42. 2026-10-11 17:13 UTCEG score recompute
  43. 2026-10-11 14:44 UTCEG score recompute
  44. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  45. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  46. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  47. 2026-10-09 15:25 UTCOSV refresh
  48. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  49. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  50. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  51. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  52. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  53. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  54. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  55. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  56. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  57. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  58. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  59. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  60. 2026-09-19 22:21 UTCOSV refresh
  61. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  62. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  63. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  64. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  65. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  66. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  67. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  68. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  69. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  70. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  71. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  72. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 36th percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-27197?
CVE-2026-27197 is a critical-severity vulnerability; its CVE record was published on February 21, 2026. 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…
When was the CVE record for CVE-2026-27197 published?
The CVE record for CVE-2026-27197 was published on February 21, 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 June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-27197 actively exploited?
CVE-2026-27197 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-27197?
CVE-2026-27197 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-27197?
A fix for CVE-2026-27197 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-27197

Explore →

Is Your Infrastructure Affected by CVE-2026-27197?

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

Book a Demo →Browse All CVEs