Sign in Sign up
JA · EN · FR
SecPulse
Categories
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.

Original description

The description as published by the source.

Impact

The podman kube play command can overwrite host files when the kube file contains a ConfigMap or Secret volume mount and the volume already contains a symlink to a host file.
This allows a malicious container to write to arbitrary files on the host BUT the attacker only controls the target path not the contents that will be written to the file. The contents are defined in the yaml file by the end user.

Requirements to exploit:

podman kube play must be used with a ConfigMap or Secret volume mount AND must be run more than once on the same volume. All the attacker has to do is create the malicious symlink on the volume the first time it is started. After that all following starts would follow the symlink and write to the host location.

Patches

Fixed in podman v5.6.1
https://github.com/containers/podman/commit/43fbde4e665fe6cee6921868f04b7ccd3de5ad89

Workarounds

Don't use podman kube play with ConfigMap or Secret volume mounts.

PR with test for CI

Adding on 9/8/2025 by @TomSweeneyRedHat , this is the PR containing the test in CI: https://github.com/containers/podman/pull/27001

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

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

Check the vendor advisory for the affected versions of 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

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify 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 し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply 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. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade github.com/containers/podman/v5 to 5.6.1

    ステージング環境で 5.6.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/containers/podman/v5
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.6.1"}]}]
go github.com/containers/podman/v4
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details