Skip to content

Rancher Extensions have arbitrary file access via path traversal

High severity GitHub Reviewed Published Apr 30, 2026 in rancher/rancher

Package

gomod github.com/rancher/rancher (Go)

Affected versions

>= 2.14.0, < 2.14.1
>= 2.13.0, < 2.13.5
>= 2.12.0, < 2.12.9
>= 2.10.11, < 2.11.13

Patched versions

2.14.1
2.13.5
2.12.9
2.11.13

Description

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:

References

@samjustus samjustus published to rancher/rancher Apr 30, 2026
Published to the GitHub Advisory Database May 7, 2026
Reviewed May 7, 2026

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H

EPSS score

Weaknesses

Path Traversal: '.../...//'

The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '.../...//' (doubled triple dot slash) sequences that can resolve to a location that is outside of that directory. Learn more on MITRE.

CVE ID

CVE-2026-25705

GHSA ID

GHSA-5v3h-x4wf-5c35

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.