Servers and applications
CVE-2026-19730
podman quadlet install --replace does not fully replace the old file
- Severity
- Medium 4.2
- Published
- 13 Aug 2026
- Last changed
- 13 Aug 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 5.8.6
- Exploit chance
- 0.1% in the next 30 daysHigher than 2% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Needs local access · Only under certain conditions · Needs a user account · Needs someone to click or open something
- Attacker can
- Read some data · Change some data · Slow it down
- CVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:L- Also known as
- GHSA-fx76-2j3w-2mx6
- Sources
- Project advisories (GitHub)
Description
When running podman quadlet install --replace to replace a Quadlet file, if the original Quadlet is larger than the new Quadlet, the file would not be truncated and content from the original would be preserved. There is no risk of information leakage as the user already had access to the Quadlet in order to replace it, and in most cases, this would only lead to invalid Quadlet files (see https://github.com/podman-container-tools/podman/issues/29013). However, security-related options from the end of the old Quadlet could be included in the new Quadlet, and if the truncation resulted in a valid Quadlet file, this could result in undesirable behavior. For example, running podman quadlet install --replace to remove a single line from the end of a Quadlet - including security-sensitive content, like AddCapability - will fail, and the option will continue to be used.
Workarounds
Manually copy the quadlet files to the quadlet directory.
Affected software
| Software | Affected versions |
|---|---|
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-57231Malformed Image can trick podman run into leaking host environment variables into the containerHigh 7.5 24 Jun 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
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-19730
- GitHub Advisory Database https://github.com/advisories/GHSA-fx76-2j3w-2mx6
- github.com https://github.com/podman-container-tools/podman/security/advisories/GHSA-fx76-2j3w-2mx6