Summary
The XSLT Transformer Step creates a TransformerFactory without enabling appropriate XML security controls, allowing external entity references to be processed.
In deployments where attacker-controlled XML or XSLT reaches this step, the issue may enable unauthorized data access and denial-of-service conditions.
Affected context
The vulnerability occurs in workflows that use the XSLT Transformer Step to process XML or XSLT content through a TransformerFactory configured without secure processing options. Risk depends on whether untrusted or insufficiently validated transformation input can reach the step and whether the runtime can access sensitive local or network resources.
Exploit preconditions
- Attack surface: XSLT transformation input handled by the Transformer Step
- Required access: Ability to supply or influence XML or XSLT content processed by the workflow
- Trigger point: Creation and execution of a transformation using the insufficiently secured TransformerFactory
- Why exploitation is possible: External entity resolution is not adequately restricted, allowing parser behavior to access external resources or consume excessive resources
Why this happens
The underlying flaw is insecure XML parser configuration. The XSLT Transformer Step builds a bare TransformerFactory without consistently disabling external entity resolution, external document access, and related risky behaviors.
This maps to CWE-611: Improper Restriction of XML External Entity Reference, where XML processing permits entity references to resolve against local files or network resources instead of treating transformation input as untrusted data.
Potential impact
- An attacker may read sensitive files accessible to the transformation process
- An attacker could cause outbound requests to internal or external resources
- Processing may be disrupted through resource exhaustion or denial-of-service conditions
- Exposed credentials or configuration data could support further compromise
General mitigation guidance
Mitigation generally focuses on making XML and XSLT processing secure by default and reducing trust in transformation input.
Common defensive patterns include:
- Disabling external general entities, external parameter entities, and external DTD access
- Restricting stylesheet imports, document retrieval, and URI resolution to approved sources
- Enabling secure-processing features and using an allowlist-based resource resolver
- Validating XML and XSLT input against narrowly defined schemas or policies
- Running transformation processes with least-privilege filesystem and network access
- Avoiding exposure of secrets and sensitive files to the transformation runtime
How teams detect issues like this
Detection can include static analysis for bare TransformerFactory construction and XML parser settings that leave external entity or URI resolution enabled.
Code review should examine factory feature configuration, resolver implementations, stylesheet import behavior, and whether untrusted XML can reach transformation code. Runtime controls can monitor unexpected file reads, outbound requests, excessive transformation resource use, and transformations involving unapproved external resources. Automated security review tools may help identify insecure XML configuration patterns during development.

