CVE-2025-52888 is a high-severity (CVSS 7.5) XML External Entity (XXE) vulnerability in io.qameta.allure.plugins:xunit-xml-plugin. A fix is available for io.qameta.allure.plugins:xunit-xml-plugin — see the affected versions and patch details below.
Allure 2's xunit-xml-plugin Vulnerable to Improper XXE Restriction
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-52888.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
io.qameta.allure.plugins:xunit-xml-plugin☕io.qameta.allure.plugins:junit-xml-plugin☕io.qameta.allure.plugins:trx-pluginReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Summary
A critical XML External Entity (XXE) vulnerability exists in the xunit-xml-plugin used by Allure 2. The plugin fails to securely configure the XML parser (DocumentBuilderFactory) and allows external entity expansion when processing test result .xml files. This allows attackers to read arbitrary files from the file system and potentially trigger server-side request forgery (SSRF).
Details
In \allure2-main\plugins\xunit-xml-plugin\src\main\java\io\qameta\allure\xunitxml\XunitXmlPlugin.java the application uses DocumentBuilderFactory without disabling DTDs or external entities. By generating a report with a malicious xml file within it, an attacker can perform XXE to leverage SSRF, or to read system files.
PoC
To recreate this vulnerability, you need to install allure for command-line (In my POC I used a Windows 11 Machine).
- Create a folder called
allure, and within it, create a malicious XML file. I will attach my SSRF and file reading payloads, however, for the rest of the POC, I will focus on reading system files for better screenshots. ##SSRF (replace webhook link with your own)
##Reading System Files
- Put the malicious .xml file into the
alluredirectory created previously - Run the following command to run the report
allure generate C:\path\to\directory\allure -o report --clean - To view and confirm the executed payload, run
allure open report - When the report opens, confirm the payload executedby going to
Categories > Product defects > <payload response>
Impact
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.qameta.allure.plugins:xunit-xml-plugin | all versions | 2.34.1io.qameta.allure.plugins:xunit-xml-plugin:2.34.1 |
| ☕Maven | io.qameta.allure.plugins:junit-xml-plugin | all versions | 2.34.1io.qameta.allure.plugins:junit-xml-plugin:2.34.1 |
| ☕Maven | io.qameta.allure.plugins:trx-plugin | all versions | 2.34.1io.qameta.allure.plugins:trx-plugin:2.34.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.qameta.allure.plugins:xunit-xml-plugin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.qameta.allure.plugins:xunit-xml-plugin to 2.34.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-52888 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.
Frequently Asked Questions
Is CVE-2025-52888 in your dependencies?
Find it across Maven, including transitive dependencies.