Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-57231 high CVSS 7.5

Information Disclosure in github.com/containers/podman/v5 (CVE-2026-57231)

Summary

Vulnerability in github.com/containers/podman/v5 (CVE-2026-57231). Confidential information can be exposed externally. Mitigation: upgrade to 5.8.4 or later.

Original description

The description as published by the source.

Summary

An container image that contains a environment variable with just a key and no value can trick podman into passing that variable from the host into the container. This is made worse by the fact that using an asterisk (*) will cause podman to pass all host variables into the container. So essentially a malicious image can exfiltrate all podman environment variables that are set in the session from where the container is launched.

Details

podman run allows --env VAR1 or --env VAR* which will read the variable values from the current environment and then passes them into the container. However because the same parsing logic was reused for the image config env section that means that an image variable could also gain access to that.

Patch

That image spec requires the env variables to be in the form of key=value, so to address this invalid formatted variables get rejected and the container will not run.

Fixed in https://github.com/podman-container-tools/podman/commit/6c431b73dbf8e4b20b778644d7a80caebdb75050

Workaround

Do not run untrusted images. Before running an image consider inspecting the config with podman image inspect --format '{{.Config.Env}}' and check for any variables that do not have a value assigned.

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-2026-57231 has been found in github.com/containers/podman/v5.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade github.com/containers/podman/v5 to 5.8.4 or later.
If unsure, ask your IT team or search "github.com/containers/podman/v5 CVE-2026-57231" on the vendor's site.

CVE-2026-57231 (github.com/containers/podman/v5) — CWE-200 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 5.8.4 — apply immediately
Workaround: Do not run untrusted images.
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

Information disclosure (CWE-200) 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 7.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 5.8.4.

🛡️ Workaround

Workaround: Do not run untrusted images.

🔍 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 
    Do not run untrusted images.

    パッチが適用されるまでの応急処置として、Do not run untrusted images. を実施。回避策の副作用 (機能低下) を確認した上で。

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

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

  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.8.4"}]}]
go go.podman.io/podman/v6
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.0.0"}]}]
go github.com/containers/podman/v4
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
go github.com/containers/podman/v3
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
go github.com/containers/podman/v2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
go github.com/containers/podman
[{"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