Loading vulnerability…
CVE-2026-84669 is a CWE-22 path traversal vulnerability in Jenkins Allure Plugin 2.35.2 and earlier. The plugin insufficiently validates paths while serving published Allure report results. An authenticated user with Item/Read permission for a job that publishes Allure reports can cause the Jenkins controller to return files outside the intended report-result directory.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A path traversal vulnerability in Jenkins Allure Plugin versions 2.35.2 and earlier that lets an attacker with Item/Read permission on qualifying jobs read arbitrary files from the Jenkins controller file system.
A CWE-22 path traversal flaw in Jenkins Allure Plugin 2.35.2 and earlier that permits users with Item/Read access to qualifying jobs to read arbitrary files from the Jenkins controller. It has a CVSS v3.1 vector of AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
A Jenkins plugin vulnerability referenced by the 2026-09-02 Jenkins security advisory; technical details are not provided.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.