CVE-2026-55686: Podman is a tool for managing OCI containers and pods

This week

MEDIUM 5.3REMOTEUPGRADE

CVE-2026-55686 is a medium-severity flaw (CVSS 5.3) affecting podman. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Podman is a tool for managing OCI containers and pods. From 3.0.0 until 5.7.1, running a malicious container image where the WORKDIR path contains a symlink can create a directory or modify ownership on the host filesystem. Modified ownership is less likely to happen as that requires help from an untrusted/malicious process that mutates the host filesystem tree during dereferencing of the WORKDIR path, to trigger a race condition. This vulnerabil

Why this priority

Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 66%)
CISA exploited list	No
Weakness	CWE-61
Published	2026-06-26
Last modified	2026-10-25

Publisher (CNA): GitHub, Inc. · Vendor: podman project

Last updated 2026-10-25 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-06-26 17:16 UTCPublished CVE record published
2026-10-25 17:10 UTCUpdated Record last modified

podman project podman UPGRADE

Affected: >= 3.0.0 and < 5.7.1

Fixed in: 5.7.1

Safe to downgrade to: a release before 3.0.0

1. Check installed version

apt-cache policy podman || rpm -q podman || podman --version

2. UPGRADE to 5.7.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade podman

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade podman

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 3.0.0 (Debian / Ubuntu)

apt-cache madison podman sudo apt install podman=<VERSION_BEFORE_3.0.0> sudo apt-mark hold podman

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list podman sudo dnf downgrade podman-<VERSION_BEFORE_3.0.0> sudo dnf versionlock add podman

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-55686?

podman: upgrade to 5.7.1. Exact commands for each OS are on this page.

Is CVE-2026-55686 being exploited?

CVE-2026-55686 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-55686 affect?

CVE-2026-55686 affects podman. Severity is medium (CVSS 5.3). Podman is a tool for managing OCI containers and pods. From 3.0.0 until 5.7.1, running a malicious container image where the WORKDIR path contains a symlink can create a directory or modify ownership on the host filesystem. Modified ownersh

How urgent is CVE-2026-55686?

Priority 37/100. Public exploit reference; Remotely exploitable, no login, no user action

Software pages

Podman vulnerabilities

Related CVEs

CVE-2026-57231 HIGH 7.5 UPGRADE Podman is a tool for managing OCI containers and pods

References

← Back to latest CVEs