Servers and applications
CVE-2026-57231
Malformed Image can trick podman run into leaking host environment variables into the container
- Severity
- High 7.5
- Published
- 24 Jun 2026
- Last changed
- 25 Oct 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 5.8.4
- Exploit chance
- 0.4% in the next 30 daysHigher than 38% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · No login needed · No user action needed
- Attacker can
- Read data
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N- Also known as
- GHSA-4hq8-gpf5-8p68
- Sources
- NVD, Project advisories (GitHub)
Description
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.
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.
Workarounds
Do not run untrusted images. Before running an image consider inspecting the config with podman image inspect --format '{{.Config.Env}}' and check for any variables that do not have a value assigned.
Affected software
| Software | Affected versions |
|---|---|
PodmanServers and applications · cpe:a:podman_project:podman |
|
PodmanServers and applications · github:podman-container-tools/podman |
|
About Podman
daemonless OCI-compliant container runtime
- Developers who used it in the past year
- 11.1%Stack Overflow Developer Survey 2025, 2025
- GitHub stars
- 33,281GitHub, 15 Nov 2026
- Forks
- 3,458GitHub, 15 Nov 2026
- Latest release
- v6.2.0GitHub, 15 Nov 2026
- Released
- 10 Nov 2026GitHub
- Developer
- Matt HeonWikidata
- License
- Apache Software License 2.0Wikidata
- Written in
- GoWikidata
- First published on GitHub
- 1 Nov 2017GitHub
Release lines
| Release | Latest | Security fixes |
|---|---|---|
| 6.1 | 6.1.4 | Yes |
| 6.0 | 6.0.2 | Ended 12 Aug 2026 |
| 5.8 | 5.8.10 | Ended 26 Sept 2026 |
| 5.7 | 5.7.1 | Ended 12 Feb 2026 |
| 5.6 | 5.6.2 | Ended 11 Nov 2025 |
| 5.5 | 5.5.2 | Ended 15 Aug 2025 |
From endoflife.date.
Vulnerabilities in Podman
- In our list
- 19
- Published in the last 12 months
- 6
- Critical, last 12 months
- 1
- High, last 12 months
- 1
- Known exploited
- 0
- CVE-2026-121885The `podman auto-update` may restart arbitrary systemd units based from the image labelsMedium 6.5 10 Nov 2026
- CVE-2026-94603The `podman run` command can be instructed to disable almost all sandboxing - including user-requested sandboxing - by image annotationCritical 10.0 29 Sept 2026
- CVE-2026-19730podman quadlet install --replace does not fully replace the old fileMedium 4.2 13 Aug 2026
- CVE-2026-55686WORKDIR symlink traversal vulnerabilityMedium 5.3 17 Jun 2026
- CVE-2026-33414PowerShell Command Injection in Podman HyperV MachineMedium 4.0 14 Apr 2026
- CVE-2024-3056A flaw was found in Podman. This issue may allow an attacker to create a specially crafted container that, when configured to share the same IPC with at least one other container, can create a large number of IPC resources in /dev/shm. The malicious container will continue to exhaust resources until it is out-of-memory (OOM) killed. While the malicious container's cgroup will be removed, the IPC…High 7.7 2 Aug 2024
References
- NVD https://nvd.nist.gov/vuln/detail/CVE-2026-57231
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-57231
- GitHub Advisory Database https://github.com/advisories/GHSA-4hq8-gpf5-8p68
- github.com https://github.com/podman-container-tools/podman/security/advisories/GHSA-4hq8-gpf5-8p68