Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-19730 medium CVSS 4.2

Vulnerability in github.com/containers/podman/v5 (CVE-2026-19730)

Summary

Vulnerability in github.com/containers/podman/v5 (CVE-2026-19730). Risk of unauthorized operations or information disclosure. Exploitable via AddCapability. Mitigation: upgrade to 6.0.0 or later.

Original description

The description as published by the source.

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 Chr…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-19730 has been found in github.com/containers/podman/v5.
Attackers can target a specific entry point like AddCapability over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.2/10.
What to do: upgrade github.com/containers/podman/v5 to 6.0.0 or later.
If unsure, ask your IT team or search "github.com/containers/podman/v5 CVE-2026-19730" on the vendor's site.

CVE-2026-19730 (github.com/containers/podman/v5) — CWE-20 / CVSS v3 4.2
Attack vector: local
Attack surface: AddCapability
Patched: 6.0.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-20) exists in github.com/containers/podman/v5. Attackers reach the vulnerable code path via AddCapability.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/containers/podman/v5. Attack surface: AddCapability.

🔥 Severity

Severity: Medium (CVSS 4.2/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 6.0.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/containers/podman/v5' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/containers/podman/v5' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/containers/podman/v5 を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/containers/podman/v5 to 6.0.0

    ステージング環境で 6.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/containers/podman/v5
[{"type":"SEMVER","events":[{"introduced":"5.7.0"},{"fixed":"5.8.6"}]}]
Go github.com/containers/podman
[{"type":"SEMVER","events":[{"introduced":"0"}]}]
Go github.com/containers/podman/v2
[{"type":"SEMVER","events":[{"introduced":"0"}]}]
Go github.com/containers/podman/v3
[{"type":"SEMVER","events":[{"introduced":"0"}]}]
Go github.com/containers/podman/v4
[{"type":"SEMVER","events":[{"introduced":"0"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details