[From nobody Tue Aug 25 12:37:05 2026
Received: (at submit) by bugs.debian.org; 23 Aug 2026 19:12:06 +0000
X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
 (2024-03-25) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-9.9 required=4.0 tests=BAYES_00, FOURLA,
 FROMDEVELOPER, 
 NO_RELAYS,XMAILER_REPORTBUG autolearn=ham autolearn_force=no
 version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 50; hammy, 150; neutral, 105; spammy,
 0. spammytokens: hammytokens:0.000-+--XDebbugsCc,
 0.000-+--X-Debbugs-Cc, 0.000-+--H*F:U*carnil, 0.000-+--H*Ad:N*Bug,
 0.000-+--HTo:N*Debian
Return-path: &lt;carnil@debian.org&gt;
Received: via submission by buxtehude.debian.org with esmtp (Exim 4.96)
 (envelope-from &lt;carnil@debian.org&gt;) id 1wyDbw-00GC3H-3B
 for submit@bugs.debian.org; Sun, 23 Aug 2026 19:12:06 +0000
Content-Type: text/plain; charset=&quot;us-ascii&quot;
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Salvatore Bonaccorso &lt;carnil@debian.org&gt;
To: Debian Bug Tracking System &lt;submit@bugs.debian.org&gt;
Subject: podman: CVE-2026-19730
Message-ID: &lt;178751232402.1279987.112428294681204602.reportbug@eldamar.lan&gt;
X-Mailer: reportbug 13.2.0+nmu1
Date: Sun, 23 Aug 2026 21:12:04 +0200
Delivered-To: submit@bugs.debian.org

Source: podman
Version: 5.8.4+ds1-2
Severity: important
Tags: security upstream
X-Debbugs-Cc: carnil@debian.org, Debian Security Team &lt;team@security.debian.org&gt;

Hi,

The following vulnerability was published for podman.

CVE-2026-19730[0]:
| 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).


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities &amp; Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2026-19730
    https://www.cve.org/CVERecord?id=CVE-2026-19730
[1] https://github.com/podman-container-tools/podman/security/advisories/GHSA-fx76-2j3w-2mx6

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
]