Lookup function information discolosure in helm

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2020-11013: 1.41% estimated exploitation activity in the next 30 days; percentile 72.73 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

The Helm core maintainers have identified an information disclosure vulnerability in Helm 3.0.0-3.1.2. Impact lookup is a Helm template function introduced in Helm v3. It is able to lookup resources in the cluster to check for the existence of specific resources and get details about them. This can be used as part of the process to render templates. The documented behavior of helm template states that it does not attach to a remote cluster. However, as the recently added lookup template function circumvents this restriction and connects to the cluster even during helm template and helm install|update|delete|rollback --dry-run. The user is not notified of this behavior. Running helm template should not make calls to a cluster. This is different from install, which is presumed to have access to a cluster in order to load resources into Kubernetes. Helm 2 is unaffected by this vulnerability. A malicious chart author could inject a lookup into a chart that, when rendered through helm…

Published by the source

27 May 2021, 18:44 UTC

Last modified by the source

9 Jan 2023, 05:05 UTC

Source last checked

26 Oct 2026, 14:54 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-q8q8-93cv-v6h8

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-11013

Advisory: Lookup function information discolosure in helm
IDs: CVE-2020-11013, GHSA-q8q8-93cv-v6h8
Record: https://patchnext.com/advisories/cve-2020-11013 (revision 1, source checked 26 Oct 2026, 14:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: helm.sh/helm/v3 3.1.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go helm.sh/helm/v3: affected >= 3.0.0, < 3.1.3; fixed in 3.1.3

## Suggested inspection (read-only)
- Go helm.sh/helm/v3: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on helm.sh/helm/v3.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-q8q8-93cv-v6h8 (GitHub-reviewed advisory GHSA-q8q8-93cv-v6h8 lists affected ranges: Go helm.sh/helm/v3 >=3.0.0 <3.1.3)

Commands are suggestions: review each one before running it.