# K3s: ZIP Archive Path Traversal Vulnerability in etcd Snapshot Decompression

Advisory record · `GHSA-jxr7-mqhw-9p98`

- **Identifiers:** `GHSA-jxr7-mqhw-9p98` · `CVE-2026-54250` · `GO-2026-5973`
- **State:** Confirmed
- **Severity:** CVSS 5.8 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 14 Jul 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 14 Jul 2026, 17:54 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/k3s-io/k3s` (Go): affected `>=1.35.0-rc1, <1.35.3 || >=1.34.0-rc1, <1.34.6 || <1.33.10`; fixed in `1.35.3`, `1.34.6`, `1.33.10`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> K3s versions before 1.33.10, from 1.34.0-rc1 before 1.34.6, and from 1.35.0-rc1 before 1.35.3 are vulnerable to a path traversal flaw in etcd snapshot decompression. An attacker who can supply a zip archive with maliciously named members could cause files to be written to arbitrary locations when an administrator restores it as a compressed etcd snapshot. Upgrade to 1.33.10, 1.34.6, or 1.35.3. Until then, set the GODEBUG environment variable to enable Go's built-in insecure path protections when restoring snapshots, or manually extract the snapshot from the zip before restoring it.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.8 Medium, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:N/I:H/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0017, the 6th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:14 UTC: First seen by agentprime
- 31 Oct 2026, 14:14 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-jxr7-mqhw-9p98)

## Sources

- [GitHub Advisory Database: GHSA-jxr7-mqhw-9p98](https://github.com/advisories/GHSA-jxr7-mqhw-9p98)
- [OSV: GHSA-jxr7-mqhw-9p98](https://osv.dev/vulnerability/GHSA-jxr7-mqhw-9p98)
- <https://github.com/k3s-io/k3s/security/advisories/GHSA-jxr7-mqhw-9p98>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-54250>
- <https://github.com/k3s-io/k3s>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-jxr7-mqhw-9p98>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-jxr7-mqhw-9p98/>. Everything for agents: <https://agentprime.io/llms.txt>.
