Podman Desktop 1.1.2 updates dependencies tied to file-write, SSRF and code-execution flaws
The Important-rated update is limited to Red Hat’s x86_64 RHEL 10 package, but developer workstations running it should move to the 1.1.2-1.el10_2 build promptly.
Red Hat has issued an Important security update for its build of Podman Desktop on Red Hat Enterprise Linux 10. The advisory moves the x86_64 package to rh-podman-desktop-1.1.2-1.el10_2 and lists 24 dependency vulnerabilities, alongside the Podman Desktop 1.1.2 release for the RHEL 10.2 Extensions channel.
The affected population is narrower than the product name may suggest. RHSA-2026:57590 names only Red Hat Enterprise Linux 10 for x86_64 and the rh-podman-desktop RPM. The advisory does not identify the Podman command-line package, other RHEL major versions, or Podman Desktop installations on macOS and Windows as affected products. Platform teams should therefore inventory RHEL 10 developer workstations and shared desktops where Red Hat’s packaged GUI is installed rather than treating every Podman host as exposed.
What the 24 fixes mean in practice
Most entries are denial-of-service or resource-exhaustion flaws in components that parse JWE, WebSocket fragments, protobuf descriptors, tar archives, YAML, links and brace expansions. Those issues can crash a process or consume memory when hostile or malformed input reaches the affected library.
The higher-consequence entries broaden the reason to update. The advisory lists an extract-zip symlink-validation bypass that can permit arbitrary file writes and information disclosure; inconsistent IP-address parsing that can enable server-side request forgery and trust-boundary bypass; a DOMPurify cross-site scripting flaw described as allowing code execution; a tmp path-traversal issue; WebSocket uninitialized-memory disclosure; PostCSS and webpack-dev-server information leaks; and CRLF injection in form-data. These are dependency-level descriptions, not proof that every path is remotely reachable through Podman Desktop. They do show why Red Hat rated the combined update Important rather than treating it as routine package maintenance.
A verified update checklist
- Confirm scope. On each RHEL 10 x86_64 workstation, inventory whether the
rh-podman-desktopRPM is installed and record its current build. Systems without that RPM are outside the affected-product list in this advisory. - Confirm content access. Ensure the workstation is registered with Red Hat Subscription Management, or receives approved RHEL content through Red Hat Satellite. Red Hat’s package-update guidance identifies RHSM as the current subscription service and Satellite as the option for systems without direct internet access.
- Apply the package update through the organization’s normal RHEL package-management workflow. The fixed advisory build is
rh-podman-desktop-1.1.2-1.el10_2.x86_64. - Verify the installed NEVRA after the transaction rather than relying only on a successful update message. The installed package should be the advisory build or a newer Red Hat-supplied build; the errata page warns that more recent packages may be available.
- Restart Podman Desktop so the running application loads the updated dependencies, then perform the team’s normal smoke test for container and image operations.
Teams that stage workstation updates should prioritize machines that open untrusted project archives, connect to externally controlled services, or process configuration supplied by multiple users. The advisory was issued Aug. 20, 2026; delaying until a general desktop maintenance window leaves avoidable exposure in a developer-facing application.
sources
- RHSA-2026:57590 — Important rh-podman-desktop security, bug fix, and enhancement updateaccess.redhat.com
- How do I apply package updates to my RHEL system?access.redhat.com
comments · 0