Technical impact
The flaw arises from the Camunda external‑task‑client's DomXmlDataFormat.defaultDocumentBuilderFactory(), which does not disable external entity resolution when parsing application/xml payloads containing serialized object variables. When an attacker is able to write a process variable—such as by leveraging the Camunda REST API or other input interfaces—they can craft XML that references external entities. The affected worker JVM will resolve those entities, allowing the attacker to read arbitrary files on the host and perform out‑of‑band HTTP requests from the engine’s environment. This can expose credentials, service‑account tokens, or private key material from more restricted network segments, effectively granting the attacker data exfiltration and potential further exploitation of the Java runtime.
Affected Systems
Camunda Platform 7.24.0 versions before 7.24.14 and Camunda Platform 7.23.0 versions before 7.23.17 are vulnerable. The vulnerability exists in the camunda‑external‑task‑client component used by any worker JVM that processes external tasks and deserializes application/xml variables.
Risk and Exploitability
The CVSS v3 score of 8.7 places this issue in the high severity range. The EPSS score is currently not available, so the likelihood of exploitation is uncertain but the absence of a KEV listing suggests no widespread active exploitation yet. However, the CVE description indicates that exploitation requires the ability to inject or modify a process variable, which may be achievable through privileged API access, injection attacks, or supply chain manipulation. If achieved, the attacker can read files and trigger outbound traffic from the JVM, potentially exposing secrets and enabling pivot attacks. Therefore, the risk is significant for installations that expose the Camunda REST endpoints to untrusted actors or otherwise allow unsanitized variable creation.