Vulnerability in github.com/containers/podman/v5 (CVE-2026-55686)
Summary
Vulnerability in github.com/containers/podman/v5 (CVE-2026-55686). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 5.7.1 or later.
Original description
The description as published by the source.
Podman is a tool for managing OCI containers and pods. From 3.0.0 until 5.7.1, running a malicious container image where the WORKDIR path contains a symlink can create a directory or modify ownership on the host filesystem. Modified ownership is less likely to happen as that requires help from an untrusted/malicious process that mutates the host filesystem tree during dereferencing of the WORKDIR path, to trigger a race condition. This vulnerability is fixed in 5.7.1.
Source: GitHub Security Advisories (Global) 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-2026-55686 has been found in github.com/containers/podman/v5.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade github.com/containers/podman/v5 to 5.7.1 or later.
If unsure, ask your IT team or search "github.com/containers/podman/v5 CVE-2026-55686" on the vendor's site.
CVE-2026-55686 (github.com/containers/podman/v5) — CWE-59 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 5.7.1 — apply immediately
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.
A vulnerability (CWE-59) exists in github.com/containers/podman/v5.
Check the vendor advisory for the affected versions of github.com/containers/podman/v5.
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.
Update to 5.7.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
-
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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/containers/podman/v5 to 5.7.1ステージング環境で 5.7.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-55686 podman
- Ubuntu UBUNTU-CVE-2026-55686 podman
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- web github.com
- web github.com