LiveActive security incident?Get immediate response
CVE Record

CVE-2021-32690: Repository credentials passed to alternate domain

Helm is a tool for managing Charts (packages of pre-configured Kubernetes resources). In versions of helm prior to 3.6.1, a vulnerability exists where the username and password credentials associated with a Helm repository could be passed on to another domain referenced by that Helm repository. This issue has been resolved in 3.6.1. There is a workaround through which one may check for improperly passed credentials. One may use a username and password for a Helm repository and may audit the Helm repository in order to check for another domain being used that could have received the credentials. In the `index.yaml` file for that repository, one may look for another domain in the `urls` list for the chart versions. If there is another domain found and that chart version was pulled or installed, the credentials would be passed on.

MediumCVSS 6.8Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Helm versions before 3.6.1 could send private repository usernames and passwords to another domain listed by that repository. This is mainly a credential-exposure issue, not code execution. Business urgency depends on whether authenticated Helm repositories were used and whether their chart indexes referenced other domains.

Executive priority

Treat this as a targeted credential-exposure cleanup. Prioritize environments using authenticated Helm repositories in CI/CD or production deployment workflows, especially where leaked credentials could access private charts or deployment artifacts.

Technical view

CVE-2021-32690 affects Helm before 3.6.1. Credentials tied to a Helm repository could be forwarded to another domain referenced in chart version urls in index.yaml. CVSS is 6.8 with high confidentiality impact and high attack complexity. The issue is fixed in Helm 3.6.1.

Likely exposure

Organizations are exposed if they used Helm before 3.6.1 with username/password-authenticated repositories, and those repository index.yaml files referenced another domain for chart version urls that users pulled or installed.

Exploitation context

The provided sources do not state active exploitation, and this CVE is not marked KEV. Practical impact requires a credentialed Helm repository plus an alternate domain reference in the repository index. Evidence is incomplete for real-world exploitation frequency.

Researcher notes

Validation should focus on repository configuration and historical chart usage, not generic Kubernetes exposure. The key condition is whether authenticated repository credentials were sent to chart urls hosted on a different domain before Helm 3.6.1.

Mitigation direction

  • Upgrade Helm clients to version 3.6.1 or later.
  • Audit authenticated Helm repositories for alternate domains in index.yaml urls.
  • Check vendor advisory and release notes for current guidance.
  • If exposure is suspected, follow internal credential-response procedures.

Validation and detection

  • Inventory Helm client versions used by developers and automation.
  • Identify Helm repositories configured with usernames and passwords.
  • Review repository index.yaml chart version urls for other domains.
  • Check whether affected chart versions were pulled or installed.
  • Document credential scope for any potentially exposed repository accounts.
Prepared
Confidence
high
Sources
4

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-200: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access 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-2021-32690 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
Medium
CVSS
6.8 (3.1)
Known Exploited
No
Published

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

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

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
6.8CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N2.24Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.8Medium
CVSS 3.1 vector shape for CVE-2021-32690Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
helmhelm< 3.6.1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-200 · source CWE mapping

Exposure of Sensitive Information to an Unauthorized Actor

Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.