ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-55686

Podman: WORKDIR symlink traversal vulnerability

Published Jun 18, 2026 · catalog updated Nov 3, 2026 · Podman: WORKDIR symlink traversal

Last checked Nov 5, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-55686. EPSS is 0.40%. Act only if a listed version of Podman: WORKDIR symlink traversal is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Podman: WORKDIR symlink traversal).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium5.3
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.40%
Remediation
Advisory link
Affected products
Go github.com/containers/podman/v3 · Go github.com/containers/podman/v4 · Go github.com/containers/podman/v5

### Summary Running a malicous 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. ### Patch https://github.com/podman-container-tools/podman/commit/d18e44e9abb3bf5b7294aa70806e1368fdddfdd0 ### Details This issue was fixed in podman 5.7.1 (git commit 7ce2e00ab140c11a68301f0b161f51984131a858) ### PoC The reproducer script _test1.bash_ demonstrates the vulnerability. The directory is created on the host. The container process uses the container directory as current working directory. The reproducer script _test2.bash_ demonstrates the same vulnerability. The directory is created on the host. The container process uses the container directory as current working directory. The reproducer script _test2.bash_ shows that the working directory can be different from the breakout directory. Reproducer **test1.bash** Reproducer **test2.bash** Vulnerable: podman 5.7.0 using Fedora CoreOS 43.20251120.3.0 Not vulnerable: podman 5.7.1 using Fedora CoreOS 43.20260119.1.1 ### Credits We like to thank Erik Sjölund (@eriksjolund) for reporting the security impact to us.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Go github.com/containers/podman/v30 → 3.4.7
  • Go github.com/containers/podman/v40 → 4.9.5
  • Go github.com/containers/podman/v50 → 5.7.1

How to fix CVE-2026-55686

  • Upgrade

    CVE-2026-55686 lists a fix boundary at 3.4.7. Compare the installed build with that boundary before you change production.

  • Version check

    Fixed in 3.4.7 · 2 other ranges on the advisory

  • Advisory

    Open the cve_org record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-55686. EPSS is 0.40%. Act only if a listed version of Podman: WORKDIR symlink traversal is installed.

Which versions are affected?

Compare what you have installed with 0 → 3.4.7, 0 → 4.9.5, 0 → 5.7.1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-59: Link Following; CWE-61. EPSS 0.40%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Jun 18, 2026 · Go Vulnerability Database

    Detected

    ### Summary Running a malicous 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. ### Patch https://github.com/podm

  2. Nov 3, 2026 · Go Vulnerability Database

    Fix available

    github.com/containers/podman/v5 fixed in 5.7.1

  3. Nov 3, 2026 · Go Vulnerability Database

    Fix available

    github.com/containers/podman/v5 fixed in 5.7.1

  4. Nov 3, 2026 · Go Vulnerability Database

    Fix available

    github.com/containers/podman/v4 fixed in 4.9.5

  5. Nov 3, 2026 · Go Vulnerability Database

    Fix available

    github.com/containers/podman/v3 fixed in 3.4.7

  6. Nov 3, 2026 · Go Vulnerability Database

    Updated

    ### Summary Running a malicous 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. ### Patch https://github.com/podm

Sources

References

Freshness

Last verified in this catalog Nov 4, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Go Vulnerability DatabaseNov 5, 2026
  • CVE.orgNov 4, 2026