/

CVE-2026-69101

Severity:

HIGH RISK

(7.7)

XXE Injection (CWE-611) in Datavane TIS Workflow XML

CVE-2026-69101

Deferred

Vulnerability type

Category:

XML External Entity Injection

CWE:

CWE-611

Impact:

Server-Side Request Forgery and Local File Disclosure

Severity:

HIGH RISK

(7.7)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Datavane TIS contains an XML external entity (XXE) injection vulnerability in workflow editing that can allow authenticated attackers to influence XML processed with external entities and DTD loading enabled. Under those conditions, the server may make attacker-controlled outbound requests and expose local files readable by the TIS process.

Affected context

The vulnerability occurs in Datavane TIS v5.0.0 when the workflow editing functionality processes attacker-influenced taskScript XML through an unhardened DocumentBuilderFactory. Risk is present where authenticated users can submit or modify workflow content through the doEditWorkflow endpoint and the XML parser permits external entities or DTD resolution.

Exploit preconditions

  • Attack surface: The authenticated workflow editing endpoint and its XML-processing path
  • Required access: An authenticated account with permission to submit or edit workflow task content
  • Trigger point: Processing of the supplied taskScript during the edit_workflow action
  • Why exploitation is possible: The XML parser allows external entity and DTD processing, causing references in attacker-influenced XML to be resolved by the server

Why this happens

The underlying flaw is insecure XML parser configuration. A DocumentBuilderFactory that leaves external entity resolution and DTD loading enabled treats attacker-controlled XML declarations as trusted parser instructions.

This maps to CWE-611: Improper Restriction of XML External Entity Reference, because external references can cause the application to access network resources or local files during XML parsing instead of limiting processing to the intended document content.

Potential impact

  • The server may issue outbound requests to attacker-controlled or internal network resources
  • Local files readable by the TIS process may be disclosed
  • Configuration data and database credentials may be exposed
  • Internal services may be probed through server-side request forgery
  • Compromised credentials could enable further unauthorized access or data manipulation

General mitigation guidance

Mitigation generally focuses on making XML parsing safe by default and reducing trust in workflow-supplied content.

Common defensive patterns include:

  • Disable external general entities, external parameter entities, and DTD processing when they are not required
  • Use hardened, feature-restricted XML parser configurations
  • Prefer simpler data formats or non-XML parsers where XML is unnecessary
  • Validate workflow content against a strict schema after safe parsing
  • Restrict outbound network access from the TIS process and isolate sensitive internal services
  • Run the application with least-privilege filesystem and database permissions
  • Keep credentials out of broadly readable configuration files and use managed secret storage where possible

How teams detect issues like this

Organizations can identify related risks through:

  • Static analysis rules for XML parser factories that enable DTDs or external entity resolution
  • Code review checks for XML parsing of request, workflow, or task-script content
  • Dependency and framework policy checks requiring hardened parser configurations
  • Runtime monitoring for unexpected outbound requests from TIS application processes
  • Egress controls and alerts for connections to unapproved external or internal destinations
  • Test cases that verify external entities, DTDs, and external schemas are rejected or ignored

Sources

SourceLink
github.comgithub.com/datavane/tis
github.comgithub.com/datavane/tis/commit/2a84a1b84218a303e3e0a4823023363d5a7abfa1
github.comgithub.com/datavane/tis/issues/496
vulncheck.comvulncheck.com/advisories/datavane-tis-xxe-injection-via-doeditworkflow-endpoint

Frequently asked

questions

It can be exploitable through the TIS workflow editing interface by an authenticated user who can submit attacker-influenced XML. The practical scope depends on endpoint authorization and network controls.

An attacker generally needs valid authentication and permission to invoke the workflow editing functionality or modify the relevant task content.

Configure XML parsers to reject or ignore DTDs and all external entity resolution, then apply strict schema validation to the remaining document content.

Establish secure XML parsing standards, test parser security features in CI, restrict application egress, and run the service with minimal access to files, databases, and internal networks.

Find out what's already
exploitable in your codebase.