maven package report

Is io.qameta.allure:allure-generator safe?

2 known vulnerabilities, worst severity HIGH.

cvss
8.6

how bad it is if exploited, out of 10

epss
0.50%

chance of exploitation in the next 30 days

xyz score
3.4

CyberXYZ composite, out of 10

fig. 01 — GHSA-64hm-gfwq-jppw, the advisory selected below

// advisories

GHSA-64hm-gfwq-jppw

HIGHCVE-2026-33166

The Allure report generator is vulnerable to an arbitrary file read via path traversal when processing test results. An attacker can craft a malicious result file (-result.json, -container.json, or .plist) that points an attachment source to a sensitive file on the host system. During report generation, Allure will resolve these paths and include the sensitive files in the final report.

Affected
<= 2.37.0
Fixed in
2.38.0
Weakness
CWE-22
Published
2026-03-18
Source
github

GHSANVDMITREreference

// dependencies

0 direct

Sign in for dependency paths and remediation

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so maven packages are not covered.

Checked 2026-09-22 at 01:55 UTC. The most recent advisory here was published 2026-06-19. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.
Is io.qameta.allure:allure-generator safe? maven package security report | CyberXYZ