Podman: Malformed Image can trick podman run into leaking host environment variables into the container
Collected exploitation and prediction evidence
Risk source coverageCISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.
No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.
cve-program · CVE-2026-57231
PublishedPodman 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.
- Source published
- 26 Jun 2026 16:29:02 UTC
- Source modified
- 27 Jun 2026 02:41:58 UTC
- Observed here
- 23 Oct 2026 15:48:27 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: cve-program · CVE Program Terms of Use. Source text is retained; field grouping and change labels are provided by ChangeIntel.
CVSS 3.1 · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
euvd · EUVD-2026-39807
PublishedPodman 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.
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Jun 26, 2026, 4:29:02 PM
dateUpdated: Jun 27, 2026, 2:41:58 AM
20 related source bulletins · separate from aliases
RHSA-2026:63307: Red Hat Security Advisory: Red Hat Quay 3.15.8
CVE-2026-15927 · CVE-2026-18255 · CVE-2026-44705 · CVE-2026-49477 · CVE-2026-56852 · CVE-2026-57231 · CVE-2026-59869 · CVE-2026-67214 · CVE-2026-67313 · CVE-2026-67314 · CVE-2026-67320 · CVE-2026-67321 · CVE-2026-69152 · CVE-2026-69153 · CVE-2026-73086 · CVE-2026-73088 · CVE-2026-73089
WID-SEC-W-2026-2062: Podman: Schwachstelle ermöglicht Offenlegung von Informationen
CVE-2026-57231
RHSA-2026:38504: Red Hat Security Advisory: container-tools:rhel8 security update
CVE-2026-33811 · CVE-2026-39835 · CVE-2026-57231
openSUSE-SU-2026:22089-1: Security update for podman
CVE-2026-55686 · CVE-2026-57231
SUSE-SU-2026:24233-1: Security update for podman
CVE-2026-55686 · CVE-2026-57231
SUSE-SU-2026:24378-1: Security update for podman
CVE-2025-22869 · CVE-2025-47913 · CVE-2025-47914 · CVE-2025-52881 · CVE-2025-6032 · CVE-2025-9566 · CVE-2026-34986 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-42508 · CVE-2026-55686 · CVE-2026-57231
RHSA-2026:37072: Red Hat Security Advisory: podman security, bug fix, and enhancement update
CVE-2026-25681 · CVE-2026-27136 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-39832 · CVE-2026-39835 · CVE-2026-42508 · CVE-2026-57231
RHSA-2026:29954: Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
CVE-2026-55686 · CVE-2026-57231
RHSA-2026:52968: Red Hat Security Advisory: Red Hat Quay 3.12.21
CVE-2026-13149 · CVE-2026-15927 · CVE-2026-39822 · CVE-2026-42504 · CVE-2026-54058 · CVE-2026-54060 · CVE-2026-55379 · CVE-2026-55380 · CVE-2026-57231 · CVE-2026-59197 · CVE-2026-59199 · CVE-2026-59200 · CVE-2026-59204 · CVE-2026-59205 · CVE-2026-59869 · CVE-2026-59885 · CVE-2026-59886
msrc_CVE-2026-57231: Podman: Malformed Image can trick podman run into leaking host environment variables into the container
CVE-2026-57231
RHSA-2026:69255: Red Hat Security Advisory: Red Hat Quay 3.16.6
CVE-2026-13149 · CVE-2026-15792 · CVE-2026-15927 · CVE-2026-16221 · CVE-2026-18255 · CVE-2026-32283 · CVE-2026-33818 · CVE-2026-39822 · CVE-2026-44705 · CVE-2026-49477 · CVE-2026-54058 · CVE-2026-54060 · CVE-2026-54770 · CVE-2026-55379 · CVE-2026-55380 · CVE-2026-56852 · CVE-2026-56853 · CVE-2026-56858 · CVE-2026-56859 · CVE-2026-56860 · CVE-2026-56862 · CVE-2026-57231 · CVE-2026-59197 · CVE-2026-59199 · CVE-2026-59200 · CVE-2026-59204 · CVE-2026-59205 · CVE-2026-59869 · CVE-2026-59879 · CVE-2026-59885 · CVE-2026-59886 · CVE-2026-67213 · CVE-2026-67214 · CVE-2026-67313 · CVE-2026-67314 · CVE-2026-67320 · CVE-2026-67321 · CVE-2026-69152 · CVE-2026-73086 · CVE-2026-75593 · CVE-2026-82417 · CVE-2026-84375
RHSA-2026:53520: Red Hat Security Advisory: Red Hat Quay 3.10.25
CVE-2026-13149 · CVE-2026-15927 · CVE-2026-39822 · CVE-2026-42504 · CVE-2026-54058 · CVE-2026-54060 · CVE-2026-55379 · CVE-2026-55380 · CVE-2026-57231 · CVE-2026-59197 · CVE-2026-59199 · CVE-2026-59200 · CVE-2026-59204 · CVE-2026-59205 · CVE-2026-59869 · CVE-2026-59885 · CVE-2026-59886
RHSA-2026:54395: Red Hat Security Advisory: Red Hat Quay 3.17.4
CVE-2026-6322 · CVE-2026-9277 · CVE-2026-10143 · CVE-2026-12143 · CVE-2026-13149 · CVE-2026-13676 · CVE-2026-15927 · CVE-2026-39821 · CVE-2026-39828 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-39831 · CVE-2026-39832 · CVE-2026-39835 · CVE-2026-42508 · CVE-2026-44432 · CVE-2026-44990 · CVE-2026-46597 · CVE-2026-54058 · CVE-2026-54060 · CVE-2026-55379 · CVE-2026-55380 · CVE-2026-57231 · CVE-2026-59197 · CVE-2026-59199 · CVE-2026-59200 · CVE-2026-59204 · CVE-2026-59205 · CVE-2026-59869 · CVE-2026-59885 · CVE-2026-59886 · CVE-2026-73086
SUSE-SU-2026:3662-1: Security update for podman
CVE-2026-55686 · CVE-2026-57231
RHSA-2026:50931: Red Hat Security Advisory: Red Hat Quay 3.9.25
CVE-2026-13149 · CVE-2026-15927 · CVE-2026-39822 · CVE-2026-42504 · CVE-2026-54058 · CVE-2026-54060 · CVE-2026-55379 · CVE-2026-55380 · CVE-2026-57231 · CVE-2026-59197 · CVE-2026-59199 · CVE-2026-59200 · CVE-2026-59204 · CVE-2026-59205 · CVE-2026-59869 · CVE-2026-59885 · CVE-2026-59886
SUSE-SU-2026:23205-1: Security update for podman
CVE-2026-55686 · CVE-2026-57231
RHSA-2026:44232: Red Hat Security Advisory: OpenShift Container Platform 4.22.7 bug fix and security update
CVE-2026-12505 · CVE-2026-43037 · CVE-2026-57231
openSUSE-SU-2026:11437-1: podman-6.0.2-1.1 on GA media
CVE-2026-57231
RHSA-2026:37123: Red Hat Security Advisory: podman security, bug fix, and enhancement update
CVE-2026-25681 · CVE-2026-27136 · CVE-2026-39829 · CVE-2026-39832 · CVE-2026-39835 · CVE-2026-42508 · CVE-2026-57231
RHSA-2026:70267: Red Hat Security Advisory: Red Hat Quay 3.14.9
CVE-2026-4427 · CVE-2026-6322 · CVE-2026-9277 · CVE-2026-10143 · CVE-2026-12143 · CVE-2026-13149 · CVE-2026-13676 · CVE-2026-14257 · CVE-2026-15792 · CVE-2026-15927 · CVE-2026-16221 · CVE-2026-18255 · CVE-2026-32591 · CVE-2026-33747 · CVE-2026-33748 · CVE-2026-33818 · CVE-2026-39820 · CVE-2026-39821 · CVE-2026-39822 · CVE-2026-39828 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-39831 · CVE-2026-39832 · CVE-2026-39835 · CVE-2026-42151 · CVE-2026-42154 · CVE-2026-42499 · CVE-2026-42504 · CVE-2026-42508 · CVE-2026-44432 · CVE-2026-44486 · CVE-2026-44487 · CVE-2026-44488 · CVE-2026-44492 · CVE-2026-44494 · CVE-2026-44495 · CVE-2026-44496 · CVE-2026-44705 · CVE-2026-44990 · CVE-2026-46595 · CVE-2026-46597 · CVE-2026-48526 · CVE-2026-49477 · CVE-2026-54058 · CVE-2026-54060 · CVE-2026-55379 · CVE-2026-55380 · CVE-2026-56852 · CVE-2026-56853 · CVE-2026-56858 · CVE-2026-56859 · CVE-2026-56860 · CVE-2026-56862 · CVE-2026-57231 · CVE-2026-59197 · CVE-2026-59199 · CVE-2026-59200 · CVE-2026-59204 · CVE-2026-59205 · CVE-2026-59869 · CVE-2026-59885 · CVE-2026-59886 · CVE-2026-67213 · CVE-2026-67214 · CVE-2026-67313 · CVE-2026-67314 · CVE-2026-67320 · CVE-2026-67321 · CVE-2026-69152 · CVE-2026-69153 · CVE-2026-73086 · CVE-2026-73088 · CVE-2026-73089 · CVE-2026-84375
- Source published
- Jun 26, 2026, 4:29:02 PM (timezone not stated)
- Source modified
- Jun 27, 2026, 2:41:58 AM (timezone not stated)
- Observed here
- 7 Nov 2026 12:37:57 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: euvd · ENISA EUVD · source terms and attribution apply. Source text is retained; field grouping and change labels are provided by ChangeIntel.
EUVD CVSS 3.1 · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd · CVE-2026-57231
PublishedPodman 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.
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Analyzed
Weakness classifications: CWE-200 · CWE-668
Original publisher date fields
published: 2026-06-26T17:16:34.697
lastModified: 2026-10-25T17:10:00.197
2 source CPE criteria · context only
- cpe:2.3:a:podman_project:podman:*:*:*:*:*:*:*:*
- cpe:2.3:a:podman_project:podman:6.0.0:rc1:*:*:*:*:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
- Source published
- 26 Jun 2026 17:16:34 UTC
- Source modified
- 25 Oct 2026 17:10:00 UTC
- Observed here
- 27 Oct 2026 15:15:28 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: nvd · NIST NVD usage terms; underlying source attribution retained. Source text is retained; field grouping and change labels are provided by ChangeIntel.
CVSS 3.1 · [email protected] · Secondary · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
osv · GHSA-4hq8-gpf5-8p68
Published## 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.
- Source published
- 24 Sep 2026 19:40:20 UTC
- Source modified
- 1 Oct 2026 20:55:51 UTC
- Observed here
- 24 Oct 2026 13:19:41 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · GitHub Advisory Database · CC-BY-4.0. Source text is retained; field grouping and change labels are provided by ChangeIntel.
CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Publisher rating · HIGH
osv · GO-2026-6594
PublishedPodman: Malformed Image can trick podman run into leaking host environment variables into the container in github.com/containers/libpod
- Source published
- 1 Oct 2026 20:23:38 UTC
- Source modified
- 1 Oct 2026 20:45:15 UTC
- Observed here
- 24 Oct 2026 13:19:41 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.