GHSA-FX76-2J3W-2MX6

Vulnerability from github – Published: 2026-09-24 16:28 – Updated: 2026-09-24 16:28
VLAI
Summary
podman quadlet install --replace does not fully replace the old file
Details

Impact

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. 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.

First introduced in commit 0ea4eaee70b7458bcc99d875529761faf5172651 with podman 5.7.0

Patches

a38a9b7d20915c55e6f3c451101ae72d6da33742 (fixed in 6.0.0)

d3adfdeec7d5c9eee5a6978df3bee62a866c958d d4fe9154ec6e32a02d5fcd096c4a27c38f2040f4 (for v5.8 branch, fixed in 5.8.6)

Workarounds

Manually copy the quadlet files to the quadlet directory.

Credits

Podman thanks Christopher Lusk clusk@northecho.dev (North Echo Security Research) for reporting the security impact of this problem.

Severity
4.2 (Medium)
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:L
Show details on source website
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/containers/podman/v5"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "5.7.0"
            },
            {
              "fixed": "5.8.6"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-19730"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-20",
      "CWE-459"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-09-24T16:28:26Z",
    "nvd_published_at": "2026-08-13T18:17:25Z",
    "severity": "MODERATE"
  },
  "details": "### Impact\n\nWhen 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. 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.\n\nFirst introduced in commit 0ea4eaee70b7458bcc99d875529761faf5172651 with podman 5.7.0\n\n\n### Patches\na38a9b7d20915c55e6f3c451101ae72d6da33742 (fixed in 6.0.0)\n\nd3adfdeec7d5c9eee5a6978df3bee62a866c958d d4fe9154ec6e32a02d5fcd096c4a27c38f2040f4 (for v5.8 branch, fixed in 5.8.6)\n\n### Workarounds\nManually copy the quadlet files to the quadlet directory.\n\n\n### Credits\n\nPodman thanks Christopher Lusk \u003cclusk@northecho.dev\u003e (North Echo Security Research) for reporting the security impact of this problem.",
  "id": "GHSA-fx76-2j3w-2mx6",
  "modified": "2026-09-24T16:28:26Z",
  "published": "2026-09-24T16:28:26Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/podman-container-tools/podman/security/advisories/GHSA-fx76-2j3w-2mx6"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-19730"
    },
    {
      "type": "WEB",
      "url": "https://github.com/podman-container-tools/podman/issues/29013"
    },
    {
      "type": "WEB",
      "url": "https://github.com/podman-container-tools/podman/pull/27980"
    },
    {
      "type": "WEB",
      "url": "https://github.com/podman-container-tools/podman/commit/0ea4eaee70b7458bcc99d875529761faf5172651"
    },
    {
      "type": "WEB",
      "url": "https://github.com/podman-container-tools/podman/commit/a38a9b7d20915c55e6f3c451101ae72d6da33742"
    },
    {
      "type": "WEB",
      "url": "https://github.com/podman-container-tools/podman/commit/d3adfdeec7d5c9eee5a6978df3bee62a866c958d"
    },
    {
      "type": "WEB",
      "url": "https://github.com/podman-container-tools/podman/commit/d4fe9154ec6e32a02d5fcd096c4a27c38f2040f4"
    },
    {
      "type": "WEB",
      "url": "https://access.redhat.com/errata/RHSA-2026:69961"
    },
    {
      "type": "WEB",
      "url": "https://access.redhat.com/errata/RHSA-2026:70201"
    },
    {
      "type": "WEB",
      "url": "https://access.redhat.com/security/cve/CVE-2026-19730"
    },
    {
      "type": "WEB",
      "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2508234"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/podman-container-tools/podman"
    },
    {
      "type": "WEB",
      "url": "https://github.com/podman-container-tools/podman/releases/tag/v5.8.6"
    },
    {
      "type": "WEB",
      "url": "https://github.com/podman-container-tools/podman/releases/tag/v6.0.0"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:L",
      "type": "CVSS_V3"
    }
  ],
  "summary": "podman quadlet install --replace does not fully replace the old file"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.