{"answers":{"affected":"2 open source packages ship an affected version, including io.qameta.allure:allure-generator. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33166 exists.","fix":"Upgrade io.qameta.allure:allure-generator to 2.38.0 or later.","what":"CVE-2026-33166 is a high-severity path traversal vulnerability in allure-framework allure2, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-33166 and fix it if it is affected.\n\nWhat it is: CVE-2026-33166 is a high-severity path traversal vulnerability in allure-framework allure2, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33166 exists.\n\nAffected packages and fixed versions:\n- io.qameta.allure:allure-generator (Maven): affected all versions; fixed in 2.38.0\n- io.qameta.allure:allure-generator (Maven): affected all versions; fixed in 2.38.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-33166/ (Markdown: https://insights.sbomify.com/CVE-2026-33166/index.md)","id":"CVE-2026-33166","markdown":"https://insights.sbomify.com/CVE-2026-33166/index.md","name":"CVE-2026-33166","record":{"aliases":["GHSA-64hm-gfwq-jppw"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Allure Report","requires_auth":"none","summary":"An attacker can read sensitive files on the host system by crafting malicious test result files processed by Allure Report.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"allure_report","vendor":"qameta"}],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"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 paths and include the sensitive files in the final report. Version 2.38.0 fixes the issue.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Allure Report has an Arbitrary File Read via Path Traversal in Attachment Processing (Allure 1, Allure 2, and XCTest Readers)","id":"CVE-2026-33166","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"Rails has a possible XSS vulnerability in its Action Pack debug exceptions","id":"CVE-2026-33167"},"packages":[{"ecosystem":"Maven","fixed":["2.38.0"],"introduced":["0"],"last_affected":[],"package":"io.qameta.allure:allure-generator","purl":null,"source":"GHSA-64hm-gfwq-jppw"},{"ecosystem":"Maven","fixed":["2.38.0"],"introduced":["0"],"last_affected":[],"package":"io.qameta.allure:allure-generator","purl":"pkg:maven/io.qameta.allure/allure-generator","source":"GHSA-64hm-gfwq-jppw"}],"prev":{"headline":"heap out-of-bounds write in libde265 1.0.16","id":"CVE-2026-33165"},"products":["allure2"],"published":"2026-03-20","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-24","vendors":["allure-framework"]},"summary":"An attacker can read sensitive files on the host system by crafting malicious test result files processed by Allure Report.","url":"https://insights.sbomify.com/CVE-2026-33166/"}