Controller code execution via symlink-following archive extraction
Published Mar 18, 2026 · Updated Mar 18, 2026
Link-following in Jenkins 2.554 and earlier and LTS 2.541.2 and earlier allows remote authenticated users to write arbitrary files. The standard artifact manager extracts crafted .tar and .tar.gz archives without rejecting symbolic links whose real paths escape the target directory. Item/Configure permission or control of an agent process is required; writes inherit Jenkins filesystem permissions and can deploy controller startup scripts or plugins for code execution.
Summary
What happened
Link-following in Jenkins 2.554 and earlier and LTS 2.541.2 and earlier allows remote authenticated users to write arbitrary files. The standard artifact manager extracts crafted .tar and .tar.gz archives without rejecting symbolic links whose real paths escape the target directory. Item/Configure permission or control of an agent process is required; writes inherit Jenkins filesystem permissions and can deploy controller startup scripts or plugins for code execution.
The record
- CVE
- CVE-2026-33001
- Published
- Mar 18, 2026
- Updated
- Mar 18, 2026
- Vendor
- Jenkins Project
- Product
- Jenkins
- Classifications
- CWE-61, CWE-59, CWE-22, T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 18, 2026CVE publishedPublication date reported by the CVE source.
- Mar 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo