# CVE-2026-54250: K3s: ZIP Archive Path Traversal Vulnerability in etcd Snapshot Decompression

> Attackers can write arbitrary files via malicious ZIP archives during etcd snapshot restoration, potentially leading to code execution or privilege escalation.

- **Severity:** Medium 5.8 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 25 Jun 2026
- **Updated:** 26 Jun 2026
- **Also known as:** GHSA-jxr7-mqhw-9p98, GO-2026-5973, MINI-868x-rfvr-c269, MINI-mpv5-grwp-9wmj

## What is CVE-2026-54250?

CVE-2026-54250 is a medium-severity path traversal vulnerability in k3s-io k3s, published on 25 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

K3s is a fully conformant production-ready Kubernetes distribution. Prior to 1.35.3+k3s1, 1.34.6+k3s1, v1.33.10+k3s1, a path traversal vulnerability exists in K3s's etcd snapshot decompression functionality. Zip files containing archive members with maliciously crafted names can be written to arbitrary locations on the filesystem when an administrator restores the archive as a compressed etcd snapshot. This vulnerability is fixed in 1.35.3+k3s1, 1.34.6+k3s1, v1.33.10+k3s1.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-54250?

7 open source packages ship an affected version, including github.com/k3s-io/k3s.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/k3s-io/k3s` | Go | All versions | None |
| `github.com/k3s-io/k3s` | Go | All versions | 1.33.10 |
| `github.com/k3s-io/k3s` | Go | All versions | 1.33.10 |
| `github.com/k3s-io/k3s` | Go | From 1.34.0-rc1 | 1.34.6 |
| `github.com/k3s-io/k3s` | Go | From 1.34.0-rc1 | 1.34.6 |
| `github.com/k3s-io/k3s` | Go | From 1.35.0-rc1 | 1.35.3 |
| `github.com/k3s-io/k3s` | Go | From 1.35.0-rc1 | 1.35.3 |

## How do I fix CVE-2026-54250?

Upgrade github.com/k3s-io/k3s to a fixed version for your release line: 1.33.10, 1.34.6 or 1.35.3.

## Is CVE-2026-54250 being exploited?

There is no known exploitation of CVE-2026-54250 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54250 and fix it if it is affected.

What it is: CVE-2026-54250 is a medium-severity path traversal vulnerability in k3s-io k3s, published on 25 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-54250 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/k3s-io/k3s (Go): affected all versions; no fix listed
- github.com/k3s-io/k3s (Go): affected all versions; fixed in 1.33.10
- github.com/k3s-io/k3s (Go): affected all versions; fixed in 1.33.10
- github.com/k3s-io/k3s (Go): affected from 1.34.0-rc1; fixed in 1.34.6
- github.com/k3s-io/k3s (Go): affected from 1.34.0-rc1; fixed in 1.34.6
- github.com/k3s-io/k3s (Go): affected from 1.35.0-rc1; fixed in 1.35.3
- github.com/k3s-io/k3s (Go): affected from 1.35.0-rc1; fixed in 1.35.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54250/ (Markdown: https://insights.sbomify.com/CVE-2026-54250/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54250
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54250
- OSV: https://osv.dev/vulnerability/CVE-2026-54250

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54250/
Summaries are generated and may contain mistakes; the official description above is the record.