Is io.qameta.allure:allure-generator affected by CVE-2026-33166?

Maven io.qameta.allure:allure-generator is affected in <2.38.0.

Is CVE-2026-33166 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.5%.

high

CVE-2026-33166

Q: Is CVE-2026-33166 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.5%.

Maven · io.qameta.allure:allure-generator

Summary

Allure Report has an Arbitrary File Read via Path Traversal in Attachment Processing (Allure 1, Allure 2, and XCTest Readers)

Severity: high
EPSS: 0.5% (p41)
Also known as: GHSA-64hm-gfwq-jppw
Published: 2026-03-18

References

https://github.com/allure-framework/allure2/security/advisories/GHSA-64hm-gfwq-jppw
https://nvd.nist.gov/vuln/detail/CVE-2026-33166
https://github.com/allure-framework/allure2

Is your project exposed to this? Stateward checks every dependency on every pull request and flags it only if your code actually reaches it.

Check my repo

Summarize with AI

ChatGPT Claude Perplexity

Sources: CISA KEV (public domain), OSV.dev & GitHub Advisory Database (CC-BY-4.0), FIRST EPSS, NVD/CWE (public domain). Served live from the Stateward advisory database.