{"items":[{"id":"NVI-00013233","kind":"vulnerability","title":"Podman: Malformed Image can trick podman run into leaking host environment variables into the container","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-4hq8-gpf5-8p68","CVE-2026-57231"],"plain_summary":"GitHub lists this reviewed advisory for github.com/containers/podman/v5, go.podman.io/podman/v6, github.com/containers/podman/v4, github.com/containers/podman/v3, github.com/containers/podman/v2. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-9cc84148d9cdf12c97a7a181e8518808"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-09-24T19:40:22.000Z","value":"7.5 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-9cc84148d9cdf12c97a7a181e8518808"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-9cc84148d9cdf12c97a7a181e8518808","url":"https://github.com/advisories/GHSA-4hq8-gpf5-8p68","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-4hq8-gpf5-8p68","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T07:24:52.155Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-9cc84148d9cdf12c97a7a181e8518808"],"technology":"github.com/containers/podman/v5","known_exclusions":[],"conditions_summary":"## Summary\n\nAn 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.\n\n## Details\n\npodman 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.\n\n## Patch\n\nThat 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.\n\nFixed in https://github.com/podman-container-tools/podman/commit/6c431b73dbf8e4b20b778644d7a80caebdb75050\n\n## Workaround\n\nDo not run untrusted images. Before running an image consider inspecting the config with `podman image inspect --format '{{.Config.Env}}'","public_affected_ranges":["< 5.8.4"]},{"certainty":"source_listed","source_ids":["sr-9cc84148d9cdf12c97a7a181e8518808"],"technology":"go.podman.io/podman/v6","known_exclusions":[],"conditions_summary":"## Summary\n\nAn 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.\n\n## Details\n\npodman 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.\n\n## Patch\n\nThat 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.\n\nFixed in https://github.com/podman-container-tools/podman/commit/6c431b73dbf8e4b20b778644d7a80caebdb75050\n\n## Workaround\n\nDo not run untrusted images. Before running an image consider inspecting the config with `podman image inspect --format '{{.Config.Env}}'","public_affected_ranges":["< 6.0.0"]},{"certainty":"source_listed","source_ids":["sr-9cc84148d9cdf12c97a7a181e8518808"],"technology":"github.com/containers/podman/v4","known_exclusions":[],"conditions_summary":"## Summary\n\nAn 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.\n\n## Details\n\npodman 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.\n\n## Patch\n\nThat 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.\n\nFixed in https://github.com/podman-container-tools/podman/commit/6c431b73dbf8e4b20b778644d7a80caebdb75050\n\n## Workaround\n\nDo not run untrusted images. Before running an image consider inspecting the config with `podman image inspect --format '{{.Config.Env}}'","public_affected_ranges":["<= 4.9.5"]},{"certainty":"source_listed","source_ids":["sr-9cc84148d9cdf12c97a7a181e8518808"],"technology":"github.com/containers/podman/v3","known_exclusions":[],"conditions_summary":"## Summary\n\nAn 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.\n\n## Details\n\npodman 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.\n\n## Patch\n\nThat 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.\n\nFixed in https://github.com/podman-container-tools/podman/commit/6c431b73dbf8e4b20b778644d7a80caebdb75050\n\n## Workaround\n\nDo not run untrusted images. Before running an image consider inspecting the config with `podman image inspect --format '{{.Config.Env}}'","public_affected_ranges":["<= 3.4.7"]},{"certainty":"source_listed","source_ids":["sr-9cc84148d9cdf12c97a7a181e8518808"],"technology":"github.com/containers/podman/v2","known_exclusions":[],"conditions_summary":"## Summary\n\nAn 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.\n\n## Details\n\npodman 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.\n\n## Patch\n\nThat 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.\n\nFixed in https://github.com/podman-container-tools/podman/commit/6c431b73dbf8e4b20b778644d7a80caebdb75050\n\n## Workaround\n\nDo not run untrusted images. Before running an image consider inspecting the config with `podman image inspect --format '{{.Config.Env}}'","public_affected_ranges":["<= 2.2.1"]},{"certainty":"source_listed","source_ids":["sr-9cc84148d9cdf12c97a7a181e8518808"],"technology":"github.com/containers/podman","known_exclusions":[],"conditions_summary":"## Summary\n\nAn 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.\n\n## Details\n\npodman 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.\n\n## Patch\n\nThat 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.\n\nFixed in https://github.com/podman-container-tools/podman/commit/6c431b73dbf8e4b20b778644d7a80caebdb75050\n\n## Workaround\n\nDo not run untrusted images. Before running an image consider inspecting the config with `podman image inspect --format '{{.Config.Env}}'","public_affected_ranges":[">= 1.8.1, < 5.8.4"]}],"null_published_at":"2026-11-01T07:29:12.931Z","source_updated_at":"2026-09-24T19:40:22.000Z","source_disclosed_at":"2026-09-24T19:40:20.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-01T07:24:52.155Z"}],"next_cursor":null,"snapshot_revision":"42594"}