Advisory record · GHSA-64hm-gfwq-jppw

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

CVSS 8.6 HighEPSS 0.0056 · 47th percentile

Published by the GitHub Advisory Database at 18 Mar 2026, 19:53 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
io.qameta.allure:allure-generatorMaven<2.38.02.38.0
Identifiers
GHSA-64hm-gfwq-jppw · CVE-2026-33166
Weakness (CWE)
CWE-22
Published
18 Mar 2026
Updated
25 Mar 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Allure Report (io.qameta.allure:allure-generator, Maven) versions before 2.38.0 are vulnerable to arbitrary file read via path traversal when processing attachments in Allure 1, Allure 2, and XCTest result files. An attacker who can supply a crafted result file can make report generation copy any file readable by the process into the report, which in CI/CD or uploaded-results setups could expose secrets or server files. Upgrade to version 2.38.0 or later.

Written 3 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.6 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0056, the 47th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:20 UTC First seen by agentprime
  2. 31 Oct 2026, 14:20 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.