Sentry Seer is vulnerable to a multi-stage trust-boundary violation that allows unauthenticated attacker-controlled telemetry to become code that is executed by an agent in a privileged automation environment. An external attacker can submit fabricated Sentry events without having access to the victim’s Sentry account, source repository, or infrastructure.
CVE-2026-90999
CRITICALPre-NVD 9.89.8—Trending — 5 sources updated this week
EchelonGraph scoreHIGH confidence
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-16. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(high)
- EG Risk
- 59(Track)EG Risk 59/100SSVC: Track
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 computedSeverity98% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 13%
- KEV
- Not listed
Published
September 16, 2026
Last Modified
September 18, 2026
Advisory Details (2)
Auto-updated Sep 18, 2026No patch confirmed yet. Sources: cert.
cert
VU#212479 - Sentry Seer vulnerability allows attacker-controlled input to be executed in a privileged environment
https://www.kb.cert.org/vuls/id/212479cert
VU#212479 - Sentry Seer vulnerability allows attacker-controlled input to be executed in a privileged environment
https://kb.cert.org/vuls/id/212479Vendor Advisories for CVE-2026-90999(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(5)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
- CWE-116Improper Encoding or Escaping of Output
- CWE-20Improper Input Validation
- CWE-74Improper Neutralization of Special Elements in Output Used by a Downstream Component (Injection)
- CWE-913Improper Control of Dynamically-Managed Code Resources
- CWE-94Improper Control of Generation of Code (Code Injection)
Data Freshness Timeline
(refreshed 15× in last 7d / 15× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
- 2026-09-19 06:51 UTCGHSA enrichment
- 2026-09-19 02:37 UTCGHSA enrichment
- 2026-09-18 22:22 UTCEG score recompute
- 2026-09-18 22:22 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 18:08 UTCEG score recompute
- 2026-09-18 18:08 UTCGHSA enrichment
- 2026-09-18 14:22 UTCGHSA enrichment
- 2026-09-18 13:44 UTCEG score recompute▲ 9.80
- 2026-09-18 13:44 UTCGHSA enrichment
- 2026-09-18 13:44 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-16 16:20 UTCNVD update
- 2026-09-16 15:50 UTCEG score recompute
- 2026-09-16 15:49 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-20 · CWE-94
- CVE-2003-1425EG 10.0EPSS p96HIGH
- CVE-2003-1432EG 10.0EPSS p94HIGH
- CVE-2002-1874EG 10.0HIGH
- CVE-2002-2236EG 10.0EPSS p92HIGH
- CVE-2002-2365EG 10.0HIGH
- CVE-2002-1358EG 10.0EPSS p93HIGH
- CVE-2002-1359EG 10.0EPSS p100HIGH
- CVE-2002-1360EG 10.0EPSS p93HIGH
- CVE-2002-0495EG 10.0EPSS p96HIGH
- CVE-1999-0702EG 10.0EPSS p98HIGH
Frequently asked(5)
What is CVE-2026-90999?
CVE-2026-90999 is a critical vulnerability published on September 16, 2026. Sentry Seer is vulnerable to a multi-stage trust-boundary violation that allows unauthenticated attacker-controlled telemetry to become code that is executed by an agent in a privileged automation environment. An external attacker can submit fabricated Sentry events without having access to the…
When was CVE-2026-90999 disclosed?
CVE-2026-90999 was first published in the National Vulnerability Database on September 16, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-90999 actively exploited?
CVE-2026-90999 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 87.4% of all scored CVEs.
What is the CVSS score of CVE-2026-90999?
CVE-2026-90999 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-90999?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-90999, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-90999
Is Your Infrastructure Affected by CVE-2026-90999?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.