# podman kube play symlink traversal vulnerability Advisory record · `GHSA-wp3j-xq48-xpjw` - **Identifiers:** `GHSA-wp3j-xq48-xpjw` · `CVE-2025-9566` · `GO-2025-3935` - **State:** Confirmed - **Severity:** CVSS 8.1 High - **Critical:** No - **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html) · [CWE-61](https://cwe.mitre.org/data/definitions/61.html) - **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md) · [CWE-61](https://agentprime.io/advisories/tag/cwe-61.md) - **Published:** 4 Sept 2025 - **Updated:** 3 Nov 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 4 Sept 2025, 20:01 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `github.com/containers/podman/v5` (Go): affected `<5.6.1`; fixed in `5.6.1` - `github.com/containers/podman/v4` (Go): affected `<=4.9.5`; no fixed version yet ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Podman's kube play command (Go package github.com/containers/podman/v5 before 5.6.1, and github.com/containers/podman/v4 at 4.9.5 and earlier) can overwrite host files when a ConfigMap or Secret volume mount already contains a symlink to a host file. An attacker who can run a malicious container must first create the symlink on the volume, after which repeated runs of kube play write the user-supplied contents to the host location. Upgrade v5 to 5.6.1; no fixed version is listed for v4. 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 - 8.1 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`, from CNA (redhat) - **CISA KEV:** Not listed. - **EPSS:** 0.012, the 68th percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 4 Sept 2025, 20:01 UTC: [Confirmed by GitHub Advisory Database](https://github.com/advisories/GHSA-wp3j-xq48-xpjw) - 5 Sept 2025, 19:54 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2025-9566) - 5 Sept 2025, 20:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2025-9566) - 31 Oct 2026, 14:12 UTC: First seen by agentprime - 31 Oct 2026, 14:12 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-wp3j-xq48-xpjw) ## Sources - [GitHub Advisory Database: GHSA-wp3j-xq48-xpjw](https://github.com/advisories/GHSA-wp3j-xq48-xpjw) - [OSV: GHSA-wp3j-xq48-xpjw](https://osv.dev/vulnerability/GHSA-wp3j-xq48-xpjw) - - - - - - - - - - - - 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 (), 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: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .