# CVE-2025-52888: Allure 2's xunit-xml-plugin Vulnerable to Improper XXE Restriction


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 24 Jun 2025
- **Updated:** 24 Jun 2025
- **Also known as:** GHSA-h7qf-qmf3-85qg

## What is CVE-2025-52888?

CVE-2025-52888 is a high-severity vulnerability in allure-framework allure2, published on 24 Jun 2025. 

### Official description

Allure 2 is the version 2.x branch of Allure Report, a multi-language test reporting tool. A critical XML External Entity (XXE) vulnerability exists in the xunit-xml-plugin used by Allure 2 prior to version 2.34.1. 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). Version 2.34.1 contains a patch for the issue.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

## Which versions are affected by CVE-2025-52888?

6 open source packages ship an affected version, including io.qameta.allure.plugins:junit-xml-plugin, io.qameta.allure.plugins:trx-plugin and io.qameta.allure.plugins:xunit-xml-plugin.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.qameta.allure.plugins:junit-xml-plugin` | Maven | All versions | 2.34.1 |
| `io.qameta.allure.plugins:junit-xml-plugin` | Maven | All versions | 2.34.1 |
| `io.qameta.allure.plugins:trx-plugin` | Maven | All versions | 2.34.1 |
| `io.qameta.allure.plugins:trx-plugin` | Maven | All versions | 2.34.1 |
| `io.qameta.allure.plugins:xunit-xml-plugin` | Maven | All versions | 2.34.1 |
| `io.qameta.allure.plugins:xunit-xml-plugin` | Maven | All versions | 2.34.1 |

## How do I fix CVE-2025-52888?

Upgrade io.qameta.allure.plugins:junit-xml-plugin to 2.34.1 or later.

## Is CVE-2025-52888 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52888 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-52888 and fix it if it is affected.

What it is: CVE-2025-52888 is a high-severity vulnerability in allure-framework allure2, published on 24 Jun 2025. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52888 exists.

Affected packages and fixed versions:
- io.qameta.allure.plugins:junit-xml-plugin (Maven): affected all versions; fixed in 2.34.1
- io.qameta.allure.plugins:junit-xml-plugin (Maven): affected all versions; fixed in 2.34.1
- io.qameta.allure.plugins:trx-plugin (Maven): affected all versions; fixed in 2.34.1
- io.qameta.allure.plugins:trx-plugin (Maven): affected all versions; fixed in 2.34.1
- io.qameta.allure.plugins:xunit-xml-plugin (Maven): affected all versions; fixed in 2.34.1
- io.qameta.allure.plugins:xunit-xml-plugin (Maven): affected all versions; fixed in 2.34.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-52888/ (Markdown: https://insights.sbomify.com/CVE-2025-52888/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-52888
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-52888
- OSV: https://osv.dev/vulnerability/CVE-2025-52888

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-52888/
Summaries are generated and may contain mistakes; the official description above is the record.
