By design, the Podman --env flag is intended to map host variables to a container. Due to the reuse of this parsing logic for image configuration, an attacker can craft a container image that forces the container engine to mirror sensitive host-side environment variables - such as API keys, database credentials, or tokens - directly into the container's process space upon execution. This vulnerability affects multiple versions of Podman across the v2 through v6 branches. Defenders should prioritize upgrading to patched versions or implementing strict image validation processes.

Impact

Successful exploitation allows an attacker to gain unauthorized access to sensitive host environment variables. In cloud or CI/CD environments where containers are frequently executed, this could lead to the exposure of credentials, service account tokens, or environment configuration secrets, potentially facilitating lateral movement or privilege escalation within the host or broader infrastructure.

Recommendation

• Upgrade Podman to a secure version as specified in the advisory: v5.8.4, v6.0.0, or higher depending on the deployment branch.
• Prior to execution, audit untrusted container images using the command: podman image inspect --format '{{.Config.Env}}' <image>. Identify and block images containing environment variables that lack a key-value assignment (i.e., variables not following the key=value format).
• Enforce strict policies regarding the ingestion of images from public or untrusted container registries.