LiveActive security incident?Get immediate response
CVE Record

CVE-2026-35204: Helm has a path traversal in plugin metadata version enables arbitrary file write outside Helm plugin directory

Helm is a package manager for Charts for Kubernetes. From 4.0.0 to 4.1.3, a specially crafted Helm plugin, when installed or updated, will cause Helm to write the contents of the plugin to an arbitrary filesystem location. To prevent this, validate that the plugin.yaml of the Helm plugin does not include a version: field containing POSIX dot-dot path separators ie. "/../". This vulnerability is fixed in 4.1.4.

HighCVSS 8.4Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A malicious Helm plugin can abuse its metadata so Helm writes plugin contents outside the intended plugin directory. This can overwrite files on the machine running Helm. The issue affects Helm 4.0.0 through 4.1.3 and is fixed in 4.1.4.

Executive priority

Treat this as high priority where Helm plugins are used in build, deployment, or administrative environments. The main business risk is arbitrary file overwrite on trusted automation or operator systems, not a broad remote internet-facing exposure based on the supplied evidence.

Technical view

CVE-2026-35204 is a CWE-22 path traversal in Helm plugin handling. During plugin install or update, a crafted plugin.yaml version field containing POSIX dot-dot path separators can cause arbitrary filesystem writes outside Helm’s plugin directory. The CVSS 4.0 score is 8.4 high, with local attack vector and user interaction required.

Likely exposure

Exposure is most likely on developer workstations, CI runners, and operations systems running Helm 4.0.0 to 4.1.3 that install or update Helm plugins, especially third-party plugins.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. Exploitation requires a user or automation path to install or update a specially crafted Helm plugin on an affected Helm version.

Researcher notes

The key condition is crafted plugin metadata, specifically the plugin.yaml version field using POSIX dot-dot path separators. Keep analysis focused on install/update behavior and filesystem write boundaries. The bundle names a fix commit and Helm 4.1.4 release but provides no confirmed exploitation evidence.

Mitigation direction

  • Upgrade Helm to 4.1.4 or later.
  • Review vendor guidance before applying distribution-specific fixes.
  • Do not install or update untrusted Helm plugins.
  • Validate plugin.yaml version fields for POSIX dot-dot path separators.
  • Restrict Helm plugin installation in CI and privileged automation contexts.

Validation and detection

  • Inventory systems running Helm 4.0.0 through 4.1.3.
  • Check CI pipelines and admin hosts for Helm plugin install or update workflows.
  • Review recently installed or updated Helm plugins for suspicious metadata.
  • Confirm deployed Helm binaries report version 4.1.4 or later.
  • Track Red Hat advisory applicability for Red Hat-packaged components.
Prepared
Confidence
high
Sources
9

Public sources used

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.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

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.

Open ATT&CK lookup
description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-35204 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.4 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:L/SC:H/SI:H/SA:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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
8Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.

ScoreVersionSeverityVectorExploitImpactSource
8.4CVSS 4.0HighCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:L/SC:H/SI:H/SA:H——GitHub_M
8.2CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H1.56redhat-SADP

Vulnerability scoring details

Base CVSS 4.0 score

8.4High
CVSS 4.0 vector shape for CVE-2026-35204Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:L/SC:H/SI:H/SA:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPgithub.com/helm/helm: helm.sh/helm/v4: Helm: Arbitrary file write via specially crafted plugin
other:Red Hat severity ratingcvssV3_1
  • 2026-04-09T16:01:36.464Z: Reported to Red Hat.
  • 2026-04-09T15:03:28.668Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
helmhelm>= 4.0.0, < 4.1.4Listed
Weakness

CWE details

CWE-22

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.

Open CWE intelligenceSame-CWE CVEs