CVE-2026-88794

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (26th 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: EPSS, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-102045 (ENISA EUVD) · GHSA-2rm5-3xrv-6hxh (GitHub Security Advisories)Source: ENISA EUVD

8.2EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.2Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

Enterprise Architect is vulnerable to XML External Entity (XXE) injection in the XSLT Debugger feature. When a user loads a crafted XML file containing a DOCTYPE with an external DTD reference, the parser processes external entities, allowing an attacker to read arbitrary files from the victim's filesystem.

Because vendor contact attempts were unsuccessful, the vulnerability has only been confirmed in version 17.1 but may also affect other versions.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
37
EG Risk 37/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)
Severity82% × 45%
Impact severity (EG Severity): CVSS 8.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
26th
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 (8.2): severity, escalated by confirmed exploitation. This CVE's 8.2 is its impact severity (EG Severity), not escalated.

EG Severity
8.2 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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 15, 2026

Last Modified

October 16, 2026

Advisory Details (1)

Auto-updated Oct 15, 2026
No fix on record yet.
Web page

Vulnerability in Sparx Systems Enterprise Architect software | CERT Polska

https://cert.pl/en/posts/2026/10/CVE-2026-88794

Vendor Advisories for CVE-2026-88794(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 25× 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-30 16:35 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  2. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  3. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  4. 2026-10-27 19:19 UTCEG score recompute
  5. 2026-10-27 19:19 UTCGHSA enrichmentGHSA-2rm5-3xrv-6hxh · GitHub severity HIGH
  6. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  7. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  8. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  9. 2026-10-25 13:53 UTCEG score recompute
  10. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  11. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  12. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  13. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  14. 2026-10-20 17:51 UTCEG score recompute
  15. 2026-10-20 17:51 UTCGHSA enrichmentGHSA-2rm5-3xrv-6hxh · GitHub severity HIGH
  16. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  17. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  18. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  19. 2026-10-18 03:03 UTCEG score recompute
  20. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  21. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  22. 2026-10-16 16:10 UTCGHSA enrichmentGHSA-2rm5-3xrv-6hxh · GitHub severity HIGH
  23. 2026-10-15 13:25 UTCEG score recompute
  24. 2026-10-15 12:49 UTCEG score recomputeFirst assessed: 8.2 HIGH
  25. 2026-10-15 12:47 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-88794?
CVE-2026-88794 is a high-severity vulnerability; its CVE record was published on October 15, 2026. Enterprise Architect is vulnerable to XML External Entity (XXE) injection in the XSLT Debugger feature. When a user loads a crafted XML file containing a DOCTYPE with an external DTD reference, the parser processes external entities, allowing an attacker to read arbitrary files from the victim's…
When was the CVE record for CVE-2026-88794 published?
The CVE record for CVE-2026-88794 was published on October 15, 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 16, 2026; the record at its source may have been updated since.
Is CVE-2026-88794 actively exploited?
CVE-2026-88794 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (26th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-88794?
CVE-2026-88794 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-88794?
No fix for CVE-2026-88794 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-88794 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-88794?

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