https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 07 Oct 2026 21:19:58 +0000 https://cve.radiocsirt.org/vuln/cve-2026-57231 <p><strong>Affected:</strong> podman-container-tools podman</p> <p>Podman is a tool for managing OCI containers and pods. From 1.8.1 until 5.8.4, a 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. This vulnerability is fixed in 5.8.4 and 6.0.0.</p> <p><strong>Affected:</strong> podman-container-tools podman</p> <p>Podman is a tool for managing OCI containers and pods. From 1.8.1 until 5.8.4, a 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. This vulnerability is fixed in 5.8.4 and 6.0.0.</p> https://cve.radiocsirt.org/vuln/cve-2026-57231 https://cve.radiocsirt.org/vuln/ghsa-4hq8-gpf5-8p68 <p><strong>Affected:</strong> Go: github.com/containers/podman/v5, Go: go.podman.io/podman/v6, Go: github.com/containers/podman/v4, Go: github.com/containers/podman/v3, Go: github.com/containers/podman/v2, Go: github.com/containers/podman</p> <p>## Summary</p> <p>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.</p> <p>## Details</p> <p>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.</p> <p>## Patch</p> <p>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.</p> <p>Fixed in https://github.com/podman-container-tools/podman/commit/6c431b73dbf8e4b20b778644d7a80caebdb75050</p> <p>## Workaround</p> <p>Do not run untrusted images. Before running an image consider inspecting the config with `podman image inspect --format &#39;{{.Config.Env}}&#39; &lt;image&gt;` and check for any variables that do not have a value assigned.</p> <p><strong>Affected:</strong> Go: github.com/containers/podman/v5, Go: go.podman.io/podman/v6, Go: github.com/containers/podman/v4, Go: github.com/containers/podman/v3, Go: github.com/containers/podman/v2, Go: github.com/containers/podman</p> <p>## Summary</p> <p>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.</p> <p>## Details</p> <p>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.</p> <p>## Patch</p> <p>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.</p> <p>Fixed in https://github.com/podman-container-tools/podman/commit/6c431b73dbf8e4b20b778644d7a80caebdb75050</p> <p>## Workaround</p> <p>Do not run untrusted images. Before running an image consider inspecting the config with `podman image inspect --format &#39;{{.Config.Env}}&#39; &lt;image&gt;` and check for any variables that do not have a value assigned.</p> https://cve.radiocsirt.org/vuln/ghsa-4hq8-gpf5-8p68