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 69% 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.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.3Exploit: None knownExposed services: Not assessed

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.3MEDIUMmedium confidence
EG Risk
28
EG Risk 28/100

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%
EPSS PROB
0.4%
EPSS %ILE
32nd
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.
githubMentions a patch (unverified)🟡 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 / EcosystemFix (by version range) / 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 rangeFix by version rangeDependents
github.com/containers/podman—
  • every version on: no fix on record
—
github.com/containers/podman/v2—
  • every version on: no fix on record
—
github.com/containers/podman/v3—
  • every version through 3.4.7: no fix on record
  • every version on: no fix on record
—
github.com/containers/podman/v4—
  • every version through 4.9.5: no fix on record
  • every version on: no fix on record
—
github.com/containers/podman/v5—
  • every version up to 5.7.1: fixed in 5.7.1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
podman5.4.2+ds1-2 ... 6.1.1+ds1-1 (26 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
podman5.4.2+ds1-2 ... 5.8.1+ds1-1 (15 versions)
  • every version up to 5.8.1+ds1-2: fixed in 5.8.1+ds1-2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 33× 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 177 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Same vendor

1 shown

redhat:RHSA-2026:29954

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 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.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55686?
CVE-2026-55686 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55686?
A fix for CVE-2026-55686 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55686 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs