github.com/containers/podman/v5
Affected
- introduced
0, fixed5.8.4(semver)
Fixed versions
5.8.4
Fix
- Fixed version
5.8.4go get github.com/containers/podman/[email protected]
Advisory
Also known as: CVE-2026-57231, GO-2026-6594
Podman: Malformed Image can trick podman run into leaking host environment variables into the container
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}}' <image> and check for any variables that do not have a value assigned.
High Basis: The source's own band: HIGH
0, fixed 5.8.4 (semver)5.8.4
5.8.4go get github.com/containers/podman/[email protected]0, fixed 6.0.0 (semver)6.0.0
6.0.0go get go.podman.io/podman/[email protected]0, last affected 4.9.5 (semver)None listed
No fixed version is listed.
0, last affected 3.4.7 (semver)None listed
No fixed version is listed.
0, last affected 2.2.1 (semver)None listed
No fixed version is listed.
1.8.1 (semver)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0