CVE-2026-55686

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 76% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 vulnerability is fixed in 5.7.1.

CVSS v3
5.3
EG Score
5.3(medium)
EPSS
23.5%
KEV
Not listed

Published

June 18, 2026

Last Modified

June 26, 2026

Advisory Details (2)

Auto-updated Jun 26, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
github Patch Available🟡 PoC Available

WORKDIR symlink traversal vulnerability · Advisory · podman-container-tools/podman · GitHub

https://github.com/podman-container-tools/podman/security/advisories/GHSA-q6r4-3wmg-fwcq
github_commit

commit d18e44e9abb3 (podman-container-tools/podman)

Fix landed in podman-container-tools/podman commit d18e44e9abb3 — awaiting tagged release

https://github.com/podman-container-tools/podman/commit/d18e44e9abb3bf5b7294aa70806e1368fdddfdd0

Vendor Advisories for CVE-2026-55686(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 1 ecosystem)
Go(3)
PackageVulnerable rangeFixed inDependents
github.com/containers/podman/v3———
github.com/containers/podman/v4———
github.com/containers/podman/v5—5.7.1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 17× in last 7d / 35× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 02:39 UTCEG score recompute
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 03:34 UTCEG score recompute
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-05 04:10 UTCEG score recompute
  8. 2026-07-05 02:31 UTCEPSS rescore
  9. 2026-07-05 02:30 UTCEPSS rescore
  10. 2026-07-04 06:31 UTCEPSS rescore
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-04 04:37 UTCEG score recompute
  13. 2026-07-03 05:05 UTCEG score recompute
  14. 2026-07-02 05:56 UTCEG score recompute
  15. 2026-07-01 15:07 UTCEPSS rescore
  16. 2026-07-01 06:49 UTCEG score recompute
  17. 2026-06-30 23:22 UTCEPSS rescore
  18. 2026-06-30 07:43 UTCEG score recompute
  19. 2026-06-29 14:06 UTCEPSS rescore
  20. 2026-06-29 14:06 UTCEPSS rescore
  21. 2026-06-29 08:39 UTCEG score recompute
  22. 2026-06-28 14:07 UTCEPSS rescore
  23. 2026-06-28 09:34 UTCEG score recompute
  24. 2026-06-28 04:56 UTCEPSS rescore
  25. 2026-06-28 04:56 UTCEPSS rescore
Show 10 more
  1. 2026-06-27 10:30 UTCEG score recompute
  2. 2026-06-26 11:26 UTCEG score recompute
  3. 2026-06-25 08:45 UTCEG score recompute
  4. 2026-06-24 09:41 UTCEG score recompute
  5. 2026-06-23 10:36 UTCEG score recompute
  6. 2026-06-22 11:27 UTCEG score recompute
  7. 2026-06-21 12:07 UTCEG score recompute
  8. 2026-06-20 12:55 UTCEG score recompute
  9. 2026-06-19 13:51 UTCEG score recompute
  10. 2026-06-18 14:44 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-55686?
CVE-2026-55686 is a medium vulnerability published on June 18, 2026. 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…
When was CVE-2026-55686 disclosed?
CVE-2026-55686 was first published in the National Vulnerability Database on June 18, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55686 actively exploited?
CVE-2026-55686 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 23.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-55686?
CVE-2026-55686 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-55686?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55686, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55686

Explore →

Is Your Infrastructure Affected by CVE-2026-55686?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs