CVE-2026-19730: Podman: podman: quadlet install --replace non-truncating write retains removed host-access directives
Noroxi assessment
Priority: Monitor (action score 16/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.13% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. A user must open a link or visit a page. Special conditions such as timing or configuration are required.
- Fixed version: podman (AlmaLinux:10) 7:5.8.2-9.el10_2.alma.1; podman-docker (AlmaLinux:10) 7:5.8.2-9.el10_2.alma.1; podman-remote (AlmaLinux:10) 7:5.8.2-9.el10_2.alma.1.
Low priority for now. Upgrade to podman (AlmaLinux:10) 7:5.8.2-9.el10_2.alma.1; podman-docker (AlmaLinux:10) 7:5.8.2-9.el10_2.alma.1; podman-remote (AlmaLinux:10) 7:5.8.2-9.el10_2.alma.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The 'podman quadlet install --replace' command opens the existing destination file with O_CREATE|O_WRONLY but omits O_TRUNC. When the initial reflink copy attempt fails (common on non-reflink-capable filesystems including many RHEL default XFS configurations), the fallback in ReflinkOrCopy uses io.Copy which performs a non-truncating write. If the original Quadlet is larger than the new Quadlet, the file is not truncated and content from the original is preserved. The command completes with no warning. 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. 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. Further, with Volume Quadlets, this can include additional mounts which can cause content to be unintentionally exposed into containers. If, later, the image is updated then compromised content might be leaked to an attacker. The vulnerable code paths are in pkg/domain/infra/abi/quadlet.go (lines 338-360, O_CREATE|O_WRONLY without O_TRUNC) and vendor/go.podman.io/storage/pkg/fileutils/reflink_linux.go (lines 12-19, non-truncating io.Copy fallback).
- Published
- Aug 13, 2026
- Updated
- Nov 5, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- CWE-459
Report tools
Action score
16
Monitor
Low priority for now.
- CVSS
- 16 / 40 · 4.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · redhat
- 4.2
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
Red Hat Red Hat Ansible Automation Platform 2
- all versionsunknown
- all versionsunknown
- all versionsunknown
- all versionsunknown
Red Hat Red Hat Enterprise Linux 10
- 7:5.8.2-9.el10_2 and laternot affected · rpm
Red Hat Red Hat Enterprise Linux 8
- all versionsunknown
Red Hat Red Hat Enterprise Linux 9
- 6:5.8.2-7.el9_8 and laternot affected · rpm
Red Hat Red Hat Hardened Images
- all versionsunknown
Red Hat Red Hat OpenShift Container Platform 4
- all versionsunknown
Red Hat Red Hat OpenShift Container Platform 5
- all versionsunknown
Red Hat Red Hat OpenShift Dev Spaces
- all versionsunknown
- all versionsunknown
- all versionsunknown
Red Hat Red Hat OpenShift Virtualization 4
- all versionsunknown
Red Hat Red Hat Quay 3
- all versionsunknown
- all versionsunknown
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | podman | before 7:5.8.2-9.el10_2.alma.1 | 7:5.8.2-9.el10_2.alma.1 |
| AlmaLinux:10 | podman-docker | before 7:5.8.2-9.el10_2.alma.1 | 7:5.8.2-9.el10_2.alma.1 |
| AlmaLinux:10 | podman-remote | before 7:5.8.2-9.el10_2.alma.1 | 7:5.8.2-9.el10_2.alma.1 |
| AlmaLinux:10 | podman-tests | before 7:5.8.2-9.el10_2.alma.1 | 7:5.8.2-9.el10_2.alma.1 |
| AlmaLinux:9 | podman | before 6:5.8.2-7.el9_8 | 6:5.8.2-7.el9_8 |
| AlmaLinux:9 | podman-docker | before 6:5.8.2-7.el9_8 | 6:5.8.2-7.el9_8 |
| AlmaLinux:9 | podman-plugins | before 6:5.8.2-7.el9_8 | 6:5.8.2-7.el9_8 |
| AlmaLinux:9 | podman-remote | before 6:5.8.2-7.el9_8 | 6:5.8.2-7.el9_8 |
| AlmaLinux:9 | podman-tests | before 6:5.8.2-7.el9_8 | 6:5.8.2-7.el9_8 |
| Alpine:v3.24 | podman | before 5.8.6-r0 | 5.8.6-r0 |
| Debian:14 | podman | before 5.8.6+ds1-1 | 5.8.6+ds1-1 |
| Go | github.com/containers/podman | from 0 | — |
| Go | github.com/containers/podman/v2 | from 0 | — |
| Go | github.com/containers/podman/v3 | from 0 | — |
| Go | github.com/containers/podman/v4 | from 0 | — |
| Go | github.com/containers/podman/v5 | from 5.7.0 · before 5.8.6 | 5.8.6 |
| Red Hat:enterprise_linux:10.2 | podman | before 7:5.8.2-9.el10_2 | 7:5.8.2-9.el10_2 |
| Red Hat:enterprise_linux:10.2 | podman-debuginfo | before 7:5.8.2-9.el10_2 | 7:5.8.2-9.el10_2 |
| Red Hat:enterprise_linux:10.2 | podman-debugsource | before 7:5.8.2-9.el10_2 | 7:5.8.2-9.el10_2 |
| Red Hat:enterprise_linux:10.2 | podman-docker | before 7:5.8.2-9.el10_2 | 7:5.8.2-9.el10_2 |
| Red Hat:enterprise_linux:10.2 | podman-remote | before 7:5.8.2-9.el10_2 | 7:5.8.2-9.el10_2 |
| Red Hat:enterprise_linux:10.2 | podman-remote-debuginfo | before 7:5.8.2-9.el10_2 | 7:5.8.2-9.el10_2 |
| Red Hat:enterprise_linux:10.2 | podman-tests | before 7:5.8.2-9.el10_2 | 7:5.8.2-9.el10_2 |
| Red Hat:enterprise_linux:10.2 | podman-tests-debuginfo | before 7:5.8.2-9.el10_2 | 7:5.8.2-9.el10_2 |
+12
Same product
red hat: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-10230Samba: command injection in wins server hook script52Plan
- CVE-2026-4631Cockpit: cockpit: unauthenticated remote code execution due to ssh command-line argument injection44Plan
- CVE-2026-76578Ipa: freeipa: freeipa: unauthenticated ldap client can obtain administrator credentials via the self-managed-token aci39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-72694Aug 11, 2026 · Mrtg: mrtg daemon symlink-following chown allows local privilege escalation via pid file path manipulation28Monitor
- ← EarlierCVE-2026-19546Aug 11, 2026 · Dbi: incomplete fix for cve-2026-14380 dbi: arbitrary code execution via caller-influenced profile attribute35Monitor
- Later →CVE-2026-75032Aug 18, 2026 · Bluez: bluez: out-of-bounds read in avrcp parse_media_element and parse_media_folder25Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:podman | 6:5.8.2-7.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:podman-docker | 6:5.8.2-7.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:podman-plugins | 6:5.8.2-7.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:podman-remote | 6:5.8.2-7.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:podman-tests | 6:5.8.2-7.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| alpine:podman | 5.8.6-r0 · Alpine:v3.24 | Package registry (OSV) |
| debian:podman | 5.8.6+ds1-1 · Debian:14 | Package registry (OSV) |
| Go:github.com/containers/podman/v5 | 5.8.6 | Package registry (OSV) |
| red hat:podman | 6:5.8.2-7.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:podman-debuginfo | 6:5.8.2-7.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:podman-debugsource | 6:5.8.2-7.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:podman-docker | 6:5.8.2-7.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:podman-plugins | 6:5.8.2-7.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:podman-plugins-debuginfo | 6:5.8.2-7.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:podman-remote | 6:5.8.2-7.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:podman-remote-debuginfo | 6:5.8.2-7.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:podman-tests | 6:5.8.2-7.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:podman-tests-debuginfo | 6:5.8.2-7.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| rocky linux:podman | 6:5.8.2-7.el9_8 · Rocky Linux:9 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- A user must open a link or visit a page.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- low · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- Low
Weakness class (CWE)
CWE-459 · Incomplete CleanupCVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:L
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
- SSVC exploitation— → poc
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.