SUSE · Security update for podman
Affects SUSESource GCVE Database
Mentioned vulnerabilities
Not known to be exploited.
Data as of 27 Oct 2026, 17:11 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.9% chance of exploitation in 30 days – higher than 60% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Exploitation evidence
Disclosed: evidence found.
CVE published 20 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
Apply the security update provided by the SUSE Product Security Team for Podman to remediate these vulnerabilities. Since this is an official security update, deploying the patch will address the issues. No additional mitigation steps are indicated in the provided data.
Description
This security update for Podman addresses two vulnerabilities: a WORKDIR symlink traversal issue (CVE-2026-55686) and a vulnerability where a specially crafted image can cause Podman to leak host environment variables into the container (CVE-2026-57231). These flaws could lead to unauthorized access to host environment data and potential container escape scenarios. The update fixes these issues to improve container security.
References
- suse.com/support/security/rating/ (opens in a new tab)
- ftp.suse.com/pub/projects/security/csaf/suse-su-2026_24378-1.json (opens in a new tab)
- suse.com/support/update/announcement/2026/suse-su-202624378-1/ (opens in a new tab)
- bugzilla.suse.com/1268579 (opens in a new tab)
- bugzilla.suse.com/1269471 (opens in a new tab)
- suse.com/security/cve/CVE-2025-22869/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-47913/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-47914/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-52881/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-6032/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-9566/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-34986/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-39829/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-39830/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-42508/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-55686/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-57231/ (opens in a new tab)