Home › Intelligence › Brief
VULNERABILITY BRIEF🟡 Medium Vulnerability

XXE Information Disclosure in Sparx Systems Enterprise Architect XSLT Debugger (CVE‑2026‑88794)

A newly disclosed XXE vulnerability (CVE‑2026‑88794) in Sparx Systems Enterprise Architect’s XSLT Debugger can leak sensitive data when a user opens a crafted file. The issue underscores the importance of continuous third‑party risk monitoring and audit‑ready evidence of remediation.

LiveThreat™ Intelligence · 📅 October 17, 2026· 📰 zerodayinitiative.com
🟡
Severity
Medium
VU
Type
Vulnerability
🎯
Confidence
High
🏢
Affected
1 sector(s)
✅
Actions
4 recommended
📰
Source
zerodayinitiative.com

XXE Information Disclosure in Sparx Systems Enterprise Architect XSLT Debugger (CVE‑2026‑88794)

What It Is — A zero‑day XML External Entity (XXE) flaw in the XSLT Debugger component of Sparx Systems Enterprise Architect enables a remote attacker, after a user opens a crafted file or visits a malicious page, to force the XML parser to retrieve arbitrary URIs and embed their contents, resulting in high‑impact information disclosure.

Exploitability — Requires user interaction (malicious file or page). No public exploit code, but CVSS 5.5 (moderate) and a CVE assigned.

Affected Products — Sparx Systems Enterprise Architect (all versions that include the XSLT Debugger).

Why It Matters for Trust & Control Assurance

  • Demonstrates the need for continuous monitoring of third‑party software configurations and evidence that security patches are applied promptly.
  • Highlights a control gap in input validation and secure handling of external XML entities, a control area that maps to multiple frameworks (e.g., NIST CSF “Protect” and ISO 27001 “Secure Development”).
  • Enterprise buyers increasingly demand audit‑ready proof that vendor‑supplied components are hardened, making third‑party risk oversight a decisive factor in procurement decisions.

Recommended Actions

  • Restrict or disable the XSLT Debugger feature until a vendor‑issued fix is available.
  • Apply network‑level controls (e.g., outbound request filtering) to block unauthorized URI fetches from the application.
  • Update your third‑party risk register to flag Enterprise Architect as a high‑risk component and capture remediation evidence in a Trust Center.
  • Monitor logs for unexpected external entity resolution attempts and retain them for audit purposes.

Source: Zero Day Initiative Advisory – ZDI‑26‑779

📰 Original Source
http://www.zerodayinitiative.com/advisories/ZDI-26-779/ ↗

This LiveThreat Intelligence Brief is an independent analysis. Read the original reporting at the link above.

From the Verisq platform · Vendor Risk Hub

Point-in-time vendor reviews miss incidents like this.

Verisq AI Trust Operations replaces the annual questionnaire with continuous third-party monitoring — so vendor exposure becomes audit evidence, not a once-a-year guess.

See how Verisq AI Trust Operations works →