HighGHSA-5v3h-x4wf-5c35CVE-2026-25705GO-2026-5154

Rancher Extensions have arbitrary file access via path traversal

Published 7 May 2026 · Updated 10 Sept 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 packages

Affected
>=2.14.0 <2.14.1
Fixed in
2.14.1
Update to the fixed version for your release line, for example:go get github.com/rancher/rancher@v2.14.1
Affected
>=2.13.0 <2.13.5
Fixed in
2.13.5
Update to the fixed version for your release line, for example:go get github.com/rancher/rancher@v2.13.5
Affected
>=2.12.0 <2.12.9
Fixed in
2.12.9
Update to the fixed version for your release line, for example:go get github.com/rancher/rancher@v2.12.9
Affected
>=2.10.11 <2.11.13
Fixed in
2.11.13
Update to the fixed version for your release line, for example:go get github.com/rancher/rancher@v2.11.13

Details

Impact

A vulnerability has been identified in Rancher's Extensions where malicious code can be injected in Rancher through a path traversal in the compressedEndpoint field inside a UIPlugin deployment. A malicious UI extension could abuse that to:

  • Overwrite Rancher binaries or configuration to inject code.
  • Write to /var/lib/rancher/ to tamper with cluster state.
  • If hostPath volumes are mounted, write to the host node filesystem.
  • Use this issue to chain with other attack vectors.

By default only the administrator can deploy UI extensions, unless permissions are granted to other users. It's always recommended to only install extensions that come from sources trusted by the user.

Please consult the associated MITRE CAPEC-126 - Technique - Path Traversal for further information about this category of attack.

Patches

This vulnerability is addressed by ensuring that:

  • The file defined by the UI Plugin CR's compressedEndpoint has to be created inside the cache directory and cannot contain ../. If that is not possible, the installation will fail and the file won't be created.
  • The icons referenced by Cluster Repos' index.yaml file always resolves to a file inside the repository directory.

Patched versions of Rancher include releases v2.14.1, v2.13.5, v2.12.9, v2.11.13.

Workarounds

There is no workaround. The user must be careful about which UI Plugins they install.

Resources

If there are any questions or comments about this advisory:

Is GHSA-5v3h-x4wf-5c35 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.