← Back
CVE-2025-9566
high
CVSS 8.1
Path Traversal in github.com/containers/podman/v5 (CVE-2025-9566)
Summary
path traversal in github.com/containers/podman/v5 (CVE-2025-9566). Data can be tampered with by attackers. Mitigation: upgrade to `5.6.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-9566** has been found in github.com/containers/podman/v5.
Data can be tampered with by attackers. CVSS score: 8.1/10.
What to do: upgrade github.com/containers/podman/v5 to **5.6.1** or later.
If unsure, ask your IT team or search "github.com/containers/podman/v5 CVE-2025-9566" on the vendor's site.
CVE-2025-9566 (github.com/containers/podman/v5) — CWE-22 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Patched: `5.6.1` — apply immediately
Workaround: Don't use podman kube play with ConfigMap or Secret volume mounts.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**Path traversal** (CWE-22) exists in github.com/containers/podman/v5.
📍 Affected scope
github.com/containers/podman/v5 — .
🔥 Severity
Severity: High (CVSS 8.1/10). Data can be tampered with by attackers
🔧 How to fix
Update to **5.6.1**.
🛡️ Workaround
Workaround: Don't use podman kube play with ConfigMap or Secret volume mounts.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'github.com/containers/podman/v5' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/containers/podman/v5' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/containers/podman/v5` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Don't use podman kube play with ConfigMap or Secret volume mounts.パッチが適用されるまでの応急処置として、Don't use podman kube play with ConfigMap or Secret volume mounts. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade github.com/containers/podman/v5 to 5.6.1ステージング環境で 5.6.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/containers/podman/v5
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"5.6.1"}]}]
go
github.com/containers/podman/v4
[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"4.9.5"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-9566
- package https://github.com/containers/podman
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web https://github.com/advisories/GHSA-wp3j-xq48-xpjw
- web [email protected]