Loading story…
Helm disclosed two high-severity flaws in its plugin handling that affect versions 4.0.0 through 4.1.3, including CVE-2026-35204 and CVE-2026-35205. The first bug is a path traversal issue in plugin metadata that lets a specially crafted plugin use ../ sequences in the version field of plugin.yaml to write files outside the intended Helm plugin directory during installation or update, creating a risk of arbitrary file write on the local filesystem.
The second flaw causes Helm to fail open on plugin provenance checks, allowing installation of plugins without a .prov file even when signature verification is required. Both issues were addressed in Helm 4.1.4, with fixes published through the project release and corresponding GitHub security advisories, and users running affected Helm 4 releases are advised to upgrade to the patched version.
See real exploitation activity before you spend the cycle.
3 events from the most recent confirmed update back to the earliest known activity.
The two Helm vulnerabilities were publicly disclosed with CVE entries and GitHub security advisory references. The disclosures documented affected versions, technical impact, and the availability of fixes in Helm 4.1.4.
Helm fixed both CVE-2026-35204 and CVE-2026-35205 in version 4.1.4. The update addressed arbitrary file write outside the plugin directory via crafted plugin metadata and improper installation of unsigned plugins when provenance files are absent.
Security reports were received for two Helm flaws affecting versions 4.0.0 through 4.1.3: a path traversal issue in plugin metadata version handling (CVE-2026-35204) and a fail-open plugin verification issue when a .prov file is missing (CVE-2026-35205).
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See real exploitation activity behind this advisory so you can triage it against everything else in the queue.
2 references tracked. Mallory keeps watching after this page renders.
cvefeed.io
Open sourcecvefeed.io
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Helm corrected **CVE-2024-25620**, which lets a chart with relative-path components in its `Chart.yaml` name write files outside the intended dependency directory, and **CVE-2024-26147**, in which metadata-free malformed `index.yaml` or `plugin.yaml` files can trigger a panic. The latter can be exploited through repository processing or a malicious installed plugin; because Helm enumerates known plugins at startup, it can cause every Helm invocation to fail. The issues affect both the Helm CLI and SDK users; fixes are available in Helm **3.14.1** for the path traversal flaw and **3.14.2** for the panic condition. Red Hat shipped remediations through updates including Advanced Cluster Management for Kubernetes 2.9.3 and OpenShift GitOps 1.12.4, with related advisories covering affected OpenShift Container Platform and Advanced Cluster Security releases. Organizations should upgrade to a fixed Helm release or applicable Red Hat container updates, inspect charts and dependencies for relative-path manipulation in `Chart.yaml` names, and remove untrusted or malicious plugins; SDK consumers that cannot immediately upgrade should recover safely from panics around affected repository and plugin-processing calls.
Aug 27, 2026
Two high-severity vulnerabilities in **OpenHarness** exposed administrative functionality to remote users through the platform’s gateway and channel layers. `CVE-2026-40502` affects versions prior to commit `dd1d235` and stems from insufficient separation between local-only and remote-safe commands in the gateway handler, allowing remote gateway users with chat access to invoke sensitive administrative actions such as changing permission modes on a running instance without operator approval. The issue is classified as `CWE-862` and carries a CVSS v3.1 score vector of `AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`. A second flaw, `CVE-2026-6819`, affects HKUDS OpenHarness prior to the fix delivered in pull request `#156` and later release `v0.1.7`, exposing plugin lifecycle commands including `/plugin install`, `/plugin enable`, `/plugin disable`, and `/reload-plugins` to remote senders by default. An attacker who gains access through the channel layer could use the weakness to install or activate untrusted plugins and alter plugin trust state remotely, creating a path to full compromise of confidentiality, integrity, and availability. The vulnerability is tracked as `CWE-276` with CVSS v3.1 vector `AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`.
Jun 29, 2026
Traefik disclosed and patched multiple vulnerabilities that let unauthenticated attackers bypass authentication and authorization controls by abusing forwarded-header handling. The most severe issue, **`CVE-2026-54763`** with a **CVSS 10.0**, allows BasicAuth, DigestAuth, and ForwardAuth protections to be bypassed through underscore-variant header injection that can spoof identity or authorization context. Two related flaws, **`CVE-2026-54764`** and **`CVE-2026-54765`**, respectively enable bypass of port-based authorization checks in ForwardAuth via injected `X-Forwarded-Proto` values and leak backend context across Kubernetes Gateway API routes that share the same `Service:port`. The disclosures build on earlier high-severity Traefik ForwardAuth bugs, **`CVE-2026-35051`** and **`CVE-2026-39858`**, which exposed protected routes when Traefik was deployed behind an upstream proxy or when downstream systems normalized underscore-form headers such as `X_Forwarded_Proto` and `X_Forwarded_User`. Affected versions span Traefik v2 and v3 releases prior to the vendor fixes, including **2.11.51**, **3.6.22**, and **3.7.6** for the latest issues, with the newer bugs described as evidence that earlier header-sanitization fixes were incomplete. The flaws put services commonly protected by ForwardAuth—such as Grafana, Kibana, Portainer, Kubernetes Dashboard, internal APIs, and admin panels—at risk, although no public exploits were reported at disclosure.
Jul 10, 2026