CVE-2026-33001: Jenkins 2.554 and earlier, LTS 2.541.2 and earlier does not safely handle symbolic links during the extract...
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.
Security readout for executives and security teams
Plain-English summary
A crafted tar archive can make a vulnerable Jenkins installation write files outside the intended extraction directory. An attacker with job configuration rights, or control of an agent, could place malicious scripts or plugins on the controller, potentially compromising Jenkins and its secrets, builds, and availability.
Executive priority
Prioritize prompt remediation because exploitation could compromise the Jenkins controller, software delivery pipelines, credentials, and build integrity. Accelerate action where external contributors configure jobs, agents cross trust boundaries, or Jenkins runs with broad filesystem permissions.
Technical view
Jenkins 2.554 and earlier and LTS 2.541.2 and earlier inadequately validate symbolic links while extracting .tar or .tar.gz archives. This path traversal and symlink weakness permits filesystem writes outside the extraction destination, limited by the operating-system permissions of the Jenkins service account. CVSS 3.1 is 8.8.
Likely exposure
Exposure exists where affected Jenkins versions process attacker-influenced tar archives and the attacker has Item/Configure permission or controls an agent process. Impact depends on the Jenkins service account’s filesystem access. Internet exposure alone is insufficient based on the supplied evidence.
Exploitation context
The supplied sources describe a low-complexity, network-reachable attack requiring limited privileges and no user interaction. Successful exploitation could affect confidentiality, integrity, and availability. The bundle does not establish active exploitation, and the CVE is not identified as being in KEV.
Researcher notes
The weakness maps to CWE-22 and CWE-59: archive extraction follows crafted symbolic links and escapes the intended directory. The supplied affected-version field ambiguously lists 2.555 and 2.541.3 despite the description ending affected ranges at 2.554 and 2.541.2; confirm fixed versions directly with Jenkins.
Mitigation direction
Inventory Jenkins controllers and identify versions 2.554 or earlier and LTS 2.541.2 or earlier.
Consult the Jenkins advisory and apply its confirmed fixed release or vendor-supported update.
Restrict Item/Configure permission to trusted administrators until remediation is complete.
Isolate or disable untrusted agents and review who can control agent processes.
Limit the Jenkins service account’s filesystem permissions using least privilege.
Validation and detection
Confirm the installed Jenkins version against the vendor advisory’s affected and fixed release information.
Review authorization settings for every principal holding Item/Configure permission.
Identify agents controlled by untrusted users or connected from insufficiently trusted systems.
Inspect controller files, startup scripts, and installed plugins for unexpected recent changes.
Review relevant Jenkins and operating-system logs for suspicious archive extraction or filesystem writes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
2ADP providers
15Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-22 · source CWE mapping
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Link Resolution Before File Access ('Link Following')
Improper Link Resolution Before File Access ('Link Following') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.