Loading vulnerability…
CVE-2026-33001 affects Jenkins 2.554 and earlier and Jenkins LTS 2.541.2 and earlier. Jenkins does not safely handle symbolic links during extraction of .tar and .tar.gz archives, allowing a crafted archive to cause files to be written to arbitrary filesystem locations, constrained only by the permissions of the user account running Jenkins. The vulnerable extraction path is used on the Jenkins controller by features including the "Archive the artifacts" post-build action and the standard artifact manager-backed archiveArtifacts and archive Pipeline steps. An attacker with Item/Configure permission, or an attacker able to control agent processes, can supply a malicious archive containing symlink entries and leverage the flaw to place files outside the intended extraction directory, including into sensitive Jenkins controller paths such as JENKINS_HOME/init.groovy.d/ or JENKINS_HOME/plugins/. This can be used to achieve code execution on the controller.
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.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.