Advisory record · GHSA-wp3j-xq48-xpjw

podman kube play symlink traversal vulnerability

CVSS 8.1 HighEPSS 0.012 · 68th percentile

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.

PackageEcosystemAffectedFixed in
github.com/containers/podman/v5Go<5.6.15.6.1
github.com/containers/podman/v4Go<=4.9.5No fixed version yet
Identifiers
GHSA-wp3j-xq48-xpjw · CVE-2025-9566 · GO-2025-3935
Weakness (CWE)
CWE-22 · CWE-61
Published
4 Sept 2025
Updated
3 Nov 2026

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

ScoreRatingCVSSVectorSource
8.1 High 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H CNA (redhat)
  • CISA KEV Not listed.
  • EPSS 0.012, the 68th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 4 Sept 2025, 20:01 UTC Confirmed by GitHub Advisory Database
  2. 5 Sept 2025, 19:54 UTC Confirmed by the CVE List
  3. 5 Sept 2025, 20:15 UTC Confirmed by NVD
  4. 31 Oct 2026, 14:12 UTC First seen by agentprime
  5. 31 Oct 2026, 14:12 UTC Confirmed by OSV

Sources

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.