<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Podman on The Coders Blog</title><link>https://thecodersblog.com/tag/podman/</link><description>Recent content in Podman on The Coders Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 08 May 2026 15:05:22 +0000</lastBuildDate><atom:link href="https://thecodersblog.com/tag/podman/index.xml" rel="self" type="application/rss+xml"/><item><title>Podman Rootless Security Flaw: Copy Fail Exploit Detailed</title><link>https://thecodersblog.com/podman-rootless-containers-and-copy-fail-exploit-2026/</link><pubDate>Fri, 08 May 2026 15:05:22 +0000</pubDate><guid>https://thecodersblog.com/podman-rootless-containers-and-copy-fail-exploit-2026/</guid><description>&lt;p&gt;For years, the promise of running containers without root privileges has been a holy grail for security-conscious DevOps teams. Podman, with its daemonless architecture and strong commitment to rootless operation, has been at the forefront of this movement. It champions an environment where container workloads are contained within user namespaces, effectively isolating them from the host system. However, a recently disclosed vulnerability, dubbed &amp;ldquo;Copy Fail&amp;rdquo; (CVE-2026-31431), threatens to unravel this carefully constructed security posture, demonstrating that even the most robust isolation mechanisms can have critical blind spots. This exploit can elevate an unprivileged user to root &lt;em&gt;within&lt;/em&gt; the container, and critically, if not properly mitigated, can even lead to root on the host itself.&lt;/p&gt;</description></item></channel></rss>