LowGO-2024-2764CVE-2019-6287GHSA-6r7x-4q7g-h83j

Rancher Project Members Have Continued Access to Namespaces After Being Removed From Them in github.com/rancher/rancher

Published 5 Jun 2024 · Updated 3 Mar 2026

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 package

Affected
>=2.0.0+incompatible <2.1.6+incompatible
Fixed in
2.1.6+incompatible
Update to the fixed version for your release line, for example:go get github.com/rancher/rancher@v2.1.6+incompatible

Details

Rancher Project Members Have Continued Access to Namespaces After Being Removed From Them in github.com/rancher/rancher

Is GO-2024-2764 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 101 advisories for github.com/rancher/rancher

References

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