CVE-2026-33166: Allure 2 is the version 2.x branch of Allure Report, a multi-language test reporting tool

Q: How do I fix CVE-2026-33166?

allure report: upgrade to 2.38.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-33166 being exploited?

CVE-2026-33166 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-33166 affect?

CVE-2026-33166 affects allure report. Severity is high (CVSS 8.6). Allure 2 is the version 2.x branch of Allure Report, a multi-language test reporting tool. The Allure report generator prior to version 2.38.0 is vulnerable to an arbitrary file read via path traversal when processing test results. An attac

Q: How urgent is CVE-2026-33166?

Priority 52/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 8.6REMOTEUPGRADE

CVE-2026-33166 is a high-severity flaw (CVSS 8.6) affecting allure report. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Allure 2 is the version 2.x branch of Allure Report, a multi-language test reporting tool. The Allure report generator prior to version 2.38.0 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 path

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	8.6 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.5% (top 54%)
CISA exploited list	No
Weakness	CWE-22
Published	2026-03-20
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: qameta

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-03-20 22:16 UTCPublished CVE record published
2026-06-17 10:37 UTCUpdated Record last modified

qameta allure report UPGRADE

Affected: < 2.38.0

Fixed in: 2.38.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy allure-report || rpm -q allure-report || allure-report --version

2. UPGRADE to 2.38.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade allure-report

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade allure-report

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-33166?

allure report: upgrade to 2.38.0. Exact commands for each OS are on this page.

Is CVE-2026-33166 being exploited?

CVE-2026-33166 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-33166 affect?

CVE-2026-33166 affects allure report. Severity is high (CVSS 8.6). Allure 2 is the version 2.x branch of Allure Report, a multi-language test reporting tool. The Allure report generator prior to version 2.38.0 is vulnerable to an arbitrary file read via path traversal when processing test results. An attac

How urgent is CVE-2026-33166?

Priority 52/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

References

← Back to latest CVEs