CVE-2025-52888

Allure Report allows Improper XXE Restriction via DocumentBuilderFactory

The explained XXE vulnerability can lead to Arbitrary File Disclosure and Server-Side Request Forgery. This exploitation can also be carried out silently, meaning it can be carried out without user interaction if the tool is automated within an application, and can go undetected with a carefully crafted payload. This could allow a malicious actor to view other source codes which may contain API or product keys, internal application URLs, or other secret items. This makes it an especially high risk when ran within a CI/CD platform.

An XML parser processes external entity references in untrusted input, causing the server to fetch internal resources or remote URLs. Typical impact: local file disclosure, server-side request forgery, or denial of service.

CVE-2025-52888 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.34.1); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2025-52888? CVE-2025-52888 is a high-severity XML external entity injection (XXE) vulnerability in io.qameta.allure.plugins:xunit-xml-plugin (maven), affecting versions <= 2.34.0. It is fixed in 2.34.1. An XML parser processes external entity references in untrusted input, causing the server to fetch internal resources or remote URLs.
2. How severe is CVE-2025-52888? CVE-2025-52888 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2025-52888?
   • io.qameta.allure.plugins:xunit-xml-plugin (maven) (versions <= 2.34.0)
   • io.qameta.allure.plugins:junit-xml-plugin (maven) (versions <= 2.34.0)
   • io.qameta.allure.plugins:trx-plugin (maven) (versions <= 2.34.0)
4. Is there a fix for CVE-2025-52888? Yes. CVE-2025-52888 is fixed in 2.34.1. Upgrade to this version or later.
5. Is CVE-2025-52888 exploitable, and should I be worried? Whether CVE-2025-52888 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-52888 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-52888?
   • Upgrade io.qameta.allure.plugins:xunit-xml-plugin to 2.34.1 or later
   • Upgrade io.qameta.allure.plugins:junit-xml-plugin to 2.34.1 or later
   • Upgrade io.qameta.allure.plugins:trx-plugin to 2.34.1 or later