Jenkins FilePath.untarFrom() does not validate symlink targets when extracting TAR archives, allowing an attacker with Item/Configure permission to create symlinks from a workspace to arbitrary files on the Jenkins controller. This issue remains exploitable in versions patched for CVE-2026-33001 and CVE-2026-70427. An attacker can use this to read sensitive files from $JENKINS_HOME, including Jenkins cryptographic keys and stored credentials. Jenkins 2.576 is additionally affected by a Unicode zero-width character bypass of the blank-name validation introduced by CVE-2026-70427.
Security readout for executives and security teams
Plain-English summary
This Jenkins issue lets a user with job configuration rights abuse TAR extraction to make the controller expose sensitive local files. The described impact includes files under $JENKINS_HOME, cryptographic keys, and stored credentials. Treat this as urgent where many users can configure jobs or where Jenkins holds production secrets.
Executive priority
Prioritize this for Jenkins environments that store deployment credentials or production secrets. The business risk is credential exposure leading to broader compromise. Because official fix details are incomplete in the provided sources, reduce permissions immediately and track Jenkins guidance closely.
Technical view
FilePath.untarFrom() fails to validate symlink targets during TAR extraction, enabling symlinks from a workspace to arbitrary controller files. The record says this bypasses fixes for CVE-2026-33001 and CVE-2026-70427. Jenkins 2.576 is additionally affected by a Unicode zero-width character bypass of blank-name validation.
Likely exposure
Exposed systems are Jenkins controllers where users with Item/Configure permission can influence workspace TAR extraction. The source bundle does not provide a precise affected version range or fixed release for CVE-2026-19429.
Exploitation context
The CVE record describes low-complexity network exploitation requiring low privileges and no user interaction. KEV is false, and the provided sources do not state active exploitation in the wild.
Researcher notes
Evidence is limited to the supplied CVE description and related Jenkins advisories. The affected range appears incomplete in the bundle. Do not assume all Jenkins versions or a fixed build without vendor confirmation. The key research angle is incomplete symlink validation after prior TAR extraction fixes.
Mitigation direction
Check Jenkins security advisories for the official fix or workaround for CVE-2026-19429.
Restrict Item/Configure permission to trusted administrators until patched or mitigated.
Review jobs and plugins that extract TAR archives into workspaces.
Rotate Jenkins secrets if sensitive controller files may have been exposed.
Apply relevant Jenkins security updates when vendor guidance names a fixed version.
Validation and detection
Inventory Jenkins controller versions, especially Jenkins 2.576.
List users and groups with Item/Configure permission.
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 · low confidence lookup
CWE-184: Exact CWE lookup
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.
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.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program 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
8Timeline events
1ADP providers
4Source 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-184 · source CWE mapping
Incomplete List of Disallowed Inputs
Incomplete List of Disallowed Inputs 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.