CVE-2026-33166

描述

### Summary 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. ### Details The vulnerability exists in several plugins where attachment paths are resolved using unvalidated user input. The code uses Path.resolve() without normalizing the path or checking if the resulting file remains within the intended results directory. Affected Files and Lines: Allure2Plugin.java (Line 264): `final Path attachmentFile = source.resolve(attachment.getSource());` Allure1Plugin.java (Line 328): `final Path attachmentFile = source.resolve(attachment.getSource());` XcTestPlugin.java (Line 181): `attachments.resolve(String.format("Screenshot_%s.%s", uuid, ext))` Since `resolve()` allows absolute paths or ../ sequences to escape the base directory, any file readable by the process can be exfiltrated. ### PoC 1) Create a directory named allure-results. 2) Create a file malicious-result.json inside it: ``` { "uuid": "poc-traversal", "name": "Path Traversal PoC", "status": "passed", "attachments": [ { "name": "Sensitive Data", "source": "../../../../../../../../../../../etc/passwd", "type": "text/plain" } ] } ``` 3) run `allure generate allure-results -o allure-report` 4) The content of `/etc/passwd` will now be present in `allure-report/data/attachments/`. ### Impact This is a High Severity vulnerability. In CI/CD environments (GitHub Actions, Jenkins), an attacker submitting a Pull Request can exfiltrate server secrets, cloud credentials, or environment configuration files stored on the runner disk. It also may affect custom Allure web services where users can upload results, allowing them to read arbitrary files from the server's filesystem. Allure TestOps is not affected.

如何修補 CVE-2026-33166

要修補 CVE-2026-33166,請將受影響套件升級到下列已修補版本。

• —升級至 2.38.0 或更新版本

CVE-2026-33166 正在被利用嗎?

低 — EPSS 為 0.0%,目前沒有觀察到大規模利用活動。