Categories
CVE-2026-34045 high CVSS 8.2

Vulnerability in Podman Desktop (CVE-2026-34045)

Summary

Vulnerability in Podman Desktop (CVE-2026-34045). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.26.2 or later.

Original description

The description as published by the source.

Podman Desktop is a graphical tool for developing on containers and Kubernetes. Prior to 1.26.2, an unauthenticated HTTP server exposed by Podman Desktop allows any network attacker to remotely trigger denial-of-service conditions and extract sensitive information. By abusing missing connection limits and timeouts, an attacker can exhaust file descriptors and kernel memory, leading to application crash or full host freeze. Additionally, verbose error responses disclose internal paths and system details (including usernames on Windows), aiding further exploitation. The issue requires no authentication or user interaction and is exploitable over the network. This vulnerability is fixed in 1.26.2.

Source: NIST National Vulnerability Database NVD

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-34045 has been found in Podman Desktop.
Risk of unauthorized operations or information disclosure. CVSS score: 8.2/10.
What to do: upgrade Podman Desktop to 1.26.2 or later.
If unsure, ask your IT team or search "Podman Desktop CVE-2026-34045" on the vendor's site.

CVE-2026-34045 (Podman Desktop) — CWE-209 / CVSS v3 8.2
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.26.2 — 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-209) exists in Podman Desktop.

📍 Affected scope

Check the vendor advisory for the affected versions of Podman Desktop.

🔥 Severity

Severity: High (CVSS 8.2/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.26.2.

🛡️ 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. Audit SBOM/dependencies to find affected services.

Response actions

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

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Podman Desktop を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch
    Upgrade Podman Desktop to 1.26.2

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

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

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

References

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