How severe is GHSA-h7qf-qmf3-85qg?

GHSA-h7qf-qmf3-85qg has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-h7qf-qmf3-85qg?

GHSA-h7qf-qmf3-85qg affects the following packages: io.qameta.allure.plugins:xunit-xml-plugin (Maven), io.qameta.allure.plugins:junit-xml-plugin (Maven), io.qameta.allure.plugins:trx-plugin (Maven). Ecosystems affected: Maven.

How do I fix GHSA-h7qf-qmf3-85qg?

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 GHSA-h7qf-qmf3-85qg is resolved across your whole dependency graph.

How do I detect GHSA-h7qf-qmf3-85qg in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.qameta.allure.plugins:xunit-xml-plugin. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-h7qf-qmf3-85qg if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-h7qf-qmf3-85qg?

O3 pinpoints whether GHSA-h7qf-qmf3-85qg is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-h7qf-qmf3-85qg actively exploited in the wild?

No public exploit code has been indexed for GHSA-h7qf-qmf3-85qg yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-h7qf-qmf3-85qg?

GHSA-h7qf-qmf3-85qg has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 24th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-h7qf-qmf3-85qg?

GHSA-h7qf-qmf3-85qg is classified as XML External Entity (XXE) (CWE-611). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-h7qf-qmf3-85qg published, and has it been updated?

GHSA-h7qf-qmf3-85qg was published on June 25, 2025 and was last updated on June 25, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

GHSA-h7qf-qmf3-85qg

HIGH

Allure Report allows Improper XXE Restriction via DocumentBuilderFactory

Also known asCVE-2025-52888

Published

Jun 25, 2025

Updated

Jun 25, 2025

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk24th percentile+0.12%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

3 pkgs affected

☕io.qameta.allure.plugins:xunit-xml-plugin☕io.qameta.allure.plugins:junit-xml-plugin☕io.qameta.allure.plugins:trx-plugin

Real-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 allure directory 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

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.qameta.allure.plugins:xunit-xml-plugin`	all versions	2.34.1
☕Maven	`io.qameta.allure.plugins:junit-xml-plugin`	all versions	2.34.1
☕Maven	`io.qameta.allure.plugins:trx-plugin`	all versions	2.34.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.qameta.allure.plugins:xunit-xml-plugin. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 GHSA-h7qf-qmf3-85qg is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-h7qf-qmf3-85qg is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-h7qf-qmf3-85qg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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 entit

O3 Security · Impact-Aware SCA

Is GHSA-h7qf-qmf3-85qg in your dependencies?

O3 detects GHSA-h7qf-qmf3-85qg across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works