HighGHSA-4hq8-gpf5-8p68CVE-2026-57231GO-2026-6594

Podman: Malformed Image can trick podman run into leaking host environment variables into the container

Published 24 Sept 2026 · Updated 1 Oct 2026

Is your project on an affected github.com/containers/podman/v5?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
<5.8.4
Fixed in
5.8.4
Update to the fixed version for your release line, for example:go get github.com/containers/podman/v5@v5.8.4
Affected
<6.0.0
Fixed in
6.0.0
Update to the fixed version for your release line, for example:go get go.podman.io/podman/v6@v6.0.0
Affected
<=4.9.5
Fixed in
No fix released
Affected
<=3.4.7
Fixed in
No fix released
Affected
<=2.2.1
Fixed in
No fix released
Affected
>=1.8.1
Fixed in
No fix released

Details

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.

Is GHSA-4hq8-gpf5-8p68 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/containers/podman/v5, and gives you the command that fixes it.

More advisories for github.com/containers/podman/v5

  • LowCVE-2026-94603Podman: The `podman run` command can be instructed to disable almost all sandboxing by image annotation in github.com/containers/podman · 19 Oct 2026
  • CriticalCVE-2026-94603Podman: The `podman run` command can be instructed to disable almost all sandboxing by image annotation · 15 Oct 2026
  • LowCVE-2026-19730podman quadlet install --replace does not fully replace the old file in github.com/containers/podman · 1 Oct 2026
  • MediumCVE-2026-19730podman quadlet install --replace does not fully replace the old file · 24 Sept 2026
  • LowCVE-2026-55686Podman: WORKDIR symlink traversal vulnerability in github.com/containers/podman · 25 Jun 2026
  • LowCVE-2026-33414PowerShell Command Injection in Podman HyperV Machine in github.com/containers/podman · 25 Jun 2026
All 20 advisories for github.com/containers/podman/v5

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.