Security readout for executives and security teams
Plain-English summary
Podman Desktop versions before 1.26.2 expose an unauthenticated HTTP server that a network attacker can abuse to crash the app or potentially freeze the host. The same issue can leak internal paths and system details, including Windows usernames. The business risk is disruption to developer machines and useful reconnaissance for later attacks.
Executive priority
Treat this as a high-priority developer endpoint issue. It does not require credentials or user interaction, and the main risk is operational disruption plus leakage of system details. Prioritize exposed developer systems and any Red Hat-packaged deployments referenced by the vendor advisory.
Technical view
The issue affects Podman Desktop before 1.26.2. The exposed WebView HTTP server lacks authentication, connection limits, and timeouts, allowing file descriptor and kernel memory exhaustion. Verbose error handling discloses internal paths and system details. CVSS is 8.2 with network attack vector, no privileges, no user interaction, low confidentiality impact, and high availability impact.
Likely exposure
Exposure is most likely on developer workstations or hosts running Podman Desktop before 1.26.2 where the WebView HTTP server is reachable from untrusted networks. The source bundle does not specify default bind behavior, affected operating system scope beyond Windows disclosure details, or internet exposure prevalence.
Exploitation context
The bundle states the flaw is remotely exploitable over the network without authentication or user interaction. It supports denial of service and sensitive information disclosure. KEV is false, and the provided sources do not state active exploitation, public exploitation, or weaponized tooling.
Researcher notes
Focus validation on version state, network reachability, and service hardening posture. The evidence identifies CWE-209, CWE-284, CWE-400, and CWE-770 patterns. The bundle does not provide enough detail to assert default exposure, affected configurations, or exploitation in the wild.
Mitigation direction
- Upgrade Podman Desktop to version 1.26.2 or later.
- Apply vendor packages referenced by RHSA-2026:13867 where applicable.
- Restrict Podman Desktop WebView server reachability from untrusted networks.
- Review vendor guidance before applying compensating controls not named in advisories.
- Monitor developer hosts for crashes, freezes, or abnormal connection pressure.
Validation and detection
- Inventory hosts running Podman Desktop and record installed versions.
- Confirm all affected installations are 1.26.2 or later.
- Check whether the WebView HTTP server is reachable from untrusted network segments.
- Review logs or endpoint telemetry for recent Podman Desktop crashes or host freezes.
- Verify remediation against the GitHub and Red Hat advisories.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-209: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-770: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-34045 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H3.94.2GitHub_MCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H3.94.2redhat-SADPVulnerability scoring details
Base CVSS 3.1 score
8.2HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H
Base CVSS 3.1 score
8.2HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-04-07T22:01:34.821Z: Reported to Red Hat.
- 2026-04-07T20:52:32.438Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/podman-desktop/podman-desktop/security/advisories/GHSA-2q88-39rh-gxvvCVE reference, GitHub_M · x_refsource_CONFIRM
- https://access.redhat.com/security/cve/CVE-2026-34045CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2456283CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-34045.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
- https://access.redhat.com/errata/RHSA-2026:13867CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Generation of Error Message Containing Sensitive Information
Generation of Error Message Containing Sensitive Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.