CVE-2026-33001 is a link-following vulnerability in Jenkins affecting 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, including in archive-processing functionality associated with FilePath.untarFrom(). Crafted archives can cause files to be written outside the intended extraction directory to arbitrary filesystem locations, constrained only by the permissions of the operating system account running Jenkins. The issue arises from insufficient validation of symbolic links during archive extraction, allowing attacker-controlled archive contents to influence path resolution on the controller filesystem. In controller-side extraction scenarios, this can be abused to place malicious scripts or plugins in locations that Jenkins will later load or execute.
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.
15 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A previously patched Jenkins issue referenced as incomplete because its fix only constrained symlink creation location, not the symlink target, leaving arbitrary controller path access possible via the newly discussed flaw.
A critical arbitrary file write leading to remote code execution in Jenkins core due to improper handling of symbolic links during .tar and .tar.gz archive extraction on the controller.
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.