CVE-2026-33001: Path Traversal
Jenkins 2.554 and earlier, LTS 2.541.2 and earlier does not safely handle symbolic links during the extraction of .tar and .tar.gz archives, allowing crafted archives to write files to arbitrary locations on the filesystem, restricted only by file system access permissions of the user running Jenkins. This can be exploited to deploy malicious scripts or plugins on the controller by attackers with Item/Configure permission, or able to control agent processes.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Jenkinsto a version that resolves this vulnerability.Fixed in 2.554 and earlier - Upgrade
Upgrade
Jenkins LTSto a version that resolves this vulnerability.Fixed in 2.541.2 and earlier
Event History
Frequently Asked Questions
What is the severity of CVE-2026-33001?
CVE-2026-33001 is categorized as a high-severity vulnerability due to its potential for arbitrary file writing.
How do I fix CVE-2026-33001?
To fix CVE-2026-33001, update Jenkins to version 2.555 or later, or upgrade to LTS version 2.542.3 or later.
What versions of Jenkins are affected by CVE-2026-33001?
Jenkins versions up to 2.554 and LTS versions up to 2.541.2 are affected by CVE-2026-33001.
What kind of attack can CVE-2026-33001 facilitate?
CVE-2026-33001 can facilitate an attack that allows crafted .tar and .tar.gz archives to write files to arbitrary locations on the filesystem.
Who is vulnerable to CVE-2026-33001?
Any user running affected versions of Jenkins without proper safeguards in place is vulnerable to CVE-2026-33001.