HighGHSA-4fc7-hc63-7fjgCVE-2021-36778

Exposure of repository credentials to external third-party sources in Rancher

Published 2 May 2022 · Updated 8 Nov 2023

Is your project on an affected github.com/rancher/rancher?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=2.6.0 <2.6.3
Fixed in
2.6.3
Update to the fixed version for your release line, for example:go get github.com/rancher/rancher@v2.6.3
Affected
>=2.5.0 <2.5.12
Fixed in
2.5.12
Update to the fixed version for your release line, for example:go get github.com/rancher/rancher@v2.5.12

Details

Impact

This issue only happens when the user configures access credentials to a private repository in Rancher inside Apps & Marketplace > Repositories. It affects Rancher versions 2.5.0 up to and including 2.5.11 and from 2.6.0 up to and including 2.6.2.

An insufficient check of the same-origin policy when downloading Helm charts from a configured private repository can lead to exposure of the repository credentials to a third-party provider. This exposure happens when the private repository:

1. Does an HTTP redirect to a third-party repository or external storage provider. 2. Downloads an icon resource for the chart hosted on a third-party provider.

The address of the private repository is not leaked, only the credentials are leaked in the HTTP Authorization header in base64 format.

With the patched versions, the default behavior now is to only send the private repository credentials when subdomain or domain hostname match when following the redirect or downloading external resources.

Patches

Patched versions include releases 2.5.12, 2.6.3 and later versions.

Workarounds

1. Update Rancher to a patched version. 2. Check the Helm charts in your configured private repository for possible redirects to third-party storage, and for Helm chart icons from third-party sources. 3. Evaluate any Helm chart that might lead to the mentioned scenario and change affected credentials if deemed necessary.

References

Information about the same-origin check and how to disable it is available in Rancher documentation.

For more information

If you have any questions or comments about this advisory:

Is GHSA-4fc7-hc63-7fjg in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/rancher/rancher, and gives you the command that fixes it.

More advisories for github.com/rancher/rancher

  • LowCVE-2026-41053Rancher has over-inclusive team membership expansion in GitHub App authentication provider in github.com/rancher/rancher · 7 Jul 2026
  • LowCVE-2026-44939Rancher vulnerable to command injection through unsanitized YAML parameter in github.com/rancher/rancher · 7 Jul 2026
  • LowCVE-2026-41052Rancher has Privilege Escalation from Project Owner to Host in github.com/rancher/rancher · 7 Jul 2026
  • CriticalCVE-2026-41052Rancher has Privilege Escalation from Project Owner to Host · 1 Jul 2026
  • HighCVE-2026-41053Rancher has over-inclusive team membership expansion in GitHub App authentication provider · 1 Jul 2026
  • CriticalCVE-2026-44939Rancher vulnerable to command injection through unsanitized YAML parameter · 1 Jul 2026
All 102 advisories for github.com/rancher/rancher

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.