NVD / CVE Program· CNA GitHub_M

CVE-2020-15185: Duplicated chart entries in Helm

Noroxi assessment

Priority: Monitor (action score 10/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.88% (FIRST EPSS); higher than 59.5% of all records.
Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: helm.sh/helm (Go) 2.16.11; helm.sh/helm/v3 (Go) 3.3.2; kubernetes (SUSE:Linux Enterprise Module for Containers 15 SP1) 1.17.13-4.21.2.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to helm.sh/helm (Go) 2.16.11; helm.sh/helm/v3 (Go) 3.3.2; kubernetes (SUSE:Linux Enterprise Module for Containers 15 SP1) 1.17.13-4.21.2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In Helm before versions 2.16.11 and 3.3.2, a Helm repository can contain duplicates of the same chart, with the last one always used. If a repository is compromised, this lowers the level of access that an attacker needs to inject a bad chart into a repository. To perform this attack, an attacker must have write access to the index file (which can occur during a MITM attack on a non-SSL connection). This issue has been patched in Helm 3.3.2 and 2.16.11. A possible workaround is to manually review the index file in the Helm repository cache before installing software.

LowCVSS 2.7 · v3.1—No exploit Fix available

Published: Sep 17, 2020
Updated: Jun 16, 2026
EPSS: 0.8% · 59th percentile
CWE: CWE-74

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 10 / 40 · 2.7 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.8%

CNA vs NVD score

NVD: 2.7
CNA · GitHub_M: 2.2; 0.5 point gap

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
helm	helm	cpe:2.3:a:helm:helm

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

helm helm3.0.0 and later · before 3.3.2
helm helm2.0.0 and later · before 2.16.11

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

helm helm
- >= 2.0.0, < 2.16.11, >= 3.0.0, < 3.3.2affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Go	helm.sh/helm	before 2.16.11	2.16.11
Go	helm.sh/helm/v3	from 3.0.0 · before 3.3.2	3.3.2
SUSE:Linux Enterprise Module for Containers 15 SP1	kubernetes	before 1.17.13-4.21.2	1.17.13-4.21.2

Same product

helm: all records

Other highest-scoring records for the same primary product.

CVE-2019-18658In Helm 2.x before 2.15.2, commands that deal with loading a chart as a directory or packaging a chart provide an opportunity for a…
40Plan
CVE-2019-1010275helm Before 2.7.2 is affected by: CWE-295: Improper Certificate Validation.
39Monitor
CVE-2025-53547Helm Chart Dependency Updating With Malicious Chart.yaml Content And Symlink Can Lead To Code Execution
34Monitor

Published before and after this one in the same product

← EarlierCVE-2020-4053Jun 16, 2020 · Path Traversal in Helm Plugin Archive
27Monitor
← EarlierCVE-2020-15184Sep 17, 2020 · Aliases are never checked in Helm
10Monitor
Later →CVE-2020-15186Sep 17, 2020 · Improper sanitization of plugin names in Helm
10Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Go:helm.sh/helm	2.16.11	Package registry (OSV)
Go:helm.sh/helm/v3	3.3.2	Package registry (OSV)
suse:kubernetes	1.17.13-4.21.2 · SUSE:Linux Enterprise Module for Containers 15 SP1	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

helm/helmcommit 055dd41

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).