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.4%, top 70% 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
Trending — 3 sources updated this week
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

A fix is available — apply it.

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)
EG Risk
28(Track)
EG Risk 28/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
30%
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(2)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpodman-main-6.0.0-1.hum12026-06-25redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(7 across 3 ecosystems)
Go(5)
PackageVulnerable rangeFixed inDependents
github.com/containers/podman———
github.com/containers/podman/v2———
github.com/containers/podman/v3———
github.com/containers/podman/v4———
github.com/containers/podman/v5—5.7.1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
podman5.4.2+ds1-2 ... 5.8.3+ds1-1 (21 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
podman5.4.2+ds1-2 ... 5.8.1+ds1-1 (15 versions)5.8.1+ds1-2—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 75× 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.

Showing the most recent 100 of 130 total refreshes for this CVE.

  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-24 23:21 UTCEG score recompute
  3. 2026-08-24 23:21 UTCVendor advisory
  4. 2026-08-24 00:17 UTCVendor advisory
  5. 2026-08-23 01:13 UTCEG score recompute
  6. 2026-08-23 01:13 UTCVendor advisory
  7. 2026-08-23 00:19 UTCEPSS rescore
  8. 2026-08-21 23:49 UTCEPSS rescore
  9. 2026-08-21 07:22 UTCEG score recompute
  10. 2026-08-21 07:22 UTCVendor advisory
  11. 2026-08-20 22:55 UTCEPSS rescore
  12. 2026-08-20 08:09 UTCEG score recompute
  13. 2026-08-20 08:09 UTCVendor advisory
  14. 2026-08-19 17:04 UTCEPSS rescore
  15. 2026-08-19 07:59 UTCEG score recompute
  16. 2026-08-19 07:59 UTCVendor advisory
  17. 2026-08-18 13:48 UTCEPSS rescore
  18. 2026-08-17 15:27 UTCEG score recompute
  19. 2026-08-17 15:27 UTCVendor advisory
  20. 2026-08-17 13:47 UTCEPSS rescore
  21. 2026-08-16 16:17 UTCEG score recompute
  22. 2026-08-16 16:17 UTCVendor advisory
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 02:14 UTCEPSS rescore
  25. 2026-08-15 17:14 UTCEG score recompute
Show 75 more
  1. 2026-08-15 17:14 UTCVendor advisory
  2. 2026-08-15 01:30 UTCEPSS rescore
  3. 2026-08-14 18:06 UTCEG score recompute
  4. 2026-08-14 18:06 UTCVendor advisory
  5. 2026-08-13 22:00 UTCEPSS rescore
  6. 2026-08-13 19:02 UTCVendor advisory
  7. 2026-08-12 18:22 UTCEG score recompute
  8. 2026-08-12 18:22 UTCVendor advisory
  9. 2026-08-12 13:51 UTCEPSS rescore
  10. 2026-08-11 19:09 UTCEG score recompute
  11. 2026-08-11 19:09 UTCVendor advisory
  12. 2026-08-11 00:00 UTCEPSS rescore
  13. 2026-08-10 20:01 UTCVendor advisory
  14. 2026-08-09 20:57 UTCEG score recompute
  15. 2026-08-09 20:57 UTCVendor advisory
  16. 2026-08-09 13:46 UTCEPSS rescore
  17. 2026-08-08 21:54 UTCVendor advisory
  18. 2026-08-07 22:50 UTCEG score recompute
  19. 2026-08-07 22:50 UTCVendor advisory
  20. 2026-08-06 23:47 UTCEG score recompute
  21. 2026-08-06 23:47 UTCVendor advisory
  22. 2026-08-06 13:47 UTCEPSS rescore
  23. 2026-08-06 00:43 UTCEG score recompute
  24. 2026-08-06 00:43 UTCVendor advisory
  25. 2026-08-05 19:17 UTCEPSS rescore
  26. 2026-08-05 01:40 UTCEG score recompute
  27. 2026-08-05 01:40 UTCVendor advisory
  28. 2026-08-04 15:10 UTCEPSS rescore
  29. 2026-08-04 10:39 UTCEPSS rescore
  30. 2026-08-04 02:24 UTCEG score recompute
  31. 2026-08-04 02:24 UTCVendor advisory
  32. 2026-08-03 10:36 UTCEPSS rescore
  33. 2026-08-03 03:20 UTCVendor advisory
  34. 2026-08-02 04:16 UTCEG score recompute
  35. 2026-08-02 04:16 UTCVendor advisory
  36. 2026-08-02 02:27 UTCEPSS rescore
  37. 2026-08-01 05:12 UTCEG score recompute
  38. 2026-08-01 05:12 UTCVendor advisory
  39. 2026-08-01 04:16 UTCEPSS rescore
  40. 2026-07-31 03:52 UTCEG score recompute
  41. 2026-07-31 03:52 UTCVendor advisory
  42. 2026-07-30 16:28 UTCEPSS rescore
  43. 2026-07-30 03:09 UTCEG score recompute
  44. 2026-07-30 03:09 UTCVendor advisory
  45. 2026-07-30 01:30 UTCEPSS rescore
  46. 2026-07-29 01:46 UTCEG score recompute
  47. 2026-07-29 01:46 UTCVendor advisory
  48. 2026-07-28 15:37 UTCEPSS rescore
  49. 2026-07-27 18:07 UTCEG score recompute
  50. 2026-07-27 18:07 UTCVendor advisory
  51. 2026-07-26 17:44 UTCEG score recompute
  52. 2026-07-26 17:44 UTCVendor advisory
  53. 2026-07-26 14:54 UTCEPSS rescore
  54. 2026-07-25 14:18 UTCEPSS rescore
  55. 2026-07-24 14:18 UTCEPSS rescore
  56. 2026-07-23 14:18 UTCEPSS rescore
  57. 2026-07-23 03:20 UTCEG score recompute
  58. 2026-07-22 14:08 UTCEPSS rescore
  59. 2026-07-21 15:25 UTCEPSS rescore
  60. 2026-07-20 17:08 UTCEPSS rescore
  61. 2026-07-19 02:29 UTCEPSS rescore
  62. 2026-07-18 10:04 UTCEPSS rescore
  63. 2026-07-16 21:09 UTCVendor advisory
  64. 2026-07-16 17:03 UTCEPSS rescore
  65. 2026-07-15 18:54 UTCVendor advisory
  66. 2026-07-15 16:57 UTCEPSS rescore
  67. 2026-07-15 16:57 UTCEPSS rescore
  68. 2026-07-15 02:00 UTCEPSS rescore
  69. 2026-07-15 02:00 UTCEPSS rescore
  70. 2026-07-14 19:44 UTCVendor advisory
  71. 2026-07-13 22:31 UTCEPSS rescore
  72. 2026-07-13 20:40 UTCVendor advisory
  73. 2026-07-13 06:13 UTCEPSS rescore
  74. 2026-07-13 06:13 UTCEPSS rescore
  75. 2026-07-12 21:36 UTCVendor advisory

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 0% probability of exploitation in the next 30 days, which ranks it in the top 69.9% of all scored CVEs.
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