Skip to main content
CVE-2024-31573VulnerabilityPublished

CVE-2024-31573: XMLUnit for Java · Incorrect Resource Transfer Between Spheres

Affects XMLUnit for JavaSource CVE Database V5

0

Not known to be exploited · CVSS 4.0 Medium : upgrade to 2.10.0 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
4.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.10.0
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Upgrade org.xmlunit/xmlunit-core to 2.10.0.

Affected software

ProductAffectedFixed in
Mavenorg.xmlunit/xmlunit-corepkg:maven/org.xmlunit/xmlunit-coreOther threatsAffected
  • <2.10.0
Fixed in
  • 2.10.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-31573, organizations should immediately upgrade XMLUnit to version 2.10.0 or later where the vulnerability is fixed. If upgrading is not immediately possible, disable XSLT extension functions explicitly in the XMLUnit configuration to prevent execution of arbitrary code. Implement strict validation and sanitization of all XML inputs and stylesheets, especially those originating from untrusted or external sources. Conduct a thorough audit of all Java applications and libraries to identify usage of XMLUnit and assess exposure. Employ runtime application self-protection (RASP) or endpoint detection and response (EDR) tools to monitor for suspicious activity related to XML processing. Educate developers about the risks of processing untrusted XML and enforce secure coding practices around XML transformations. Finally, maintain up-to-date backups and incident response plans to quickly recover from potential exploitation.

Description

XMLUnit for Java before 2.10.0, in the default configuration, might allow code execution via an untrusted stylesheet (used for an XSLT transformation), because XSLT extension functions are enabled.

References

Community reviews

Loading reviews…