CVE-2014-9358

MEDIUMCVSS v2 · 6.46.4—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 6.4 — v2 rates that MEDIUM (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:L/Au:N/C:P/I:P/A:N. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 2.5% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: epss, nvd_v2
6.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 2.5%CVSS v2: 6.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Docker before 1.3.3 does not properly validate image IDs, which allows remote attackers to conduct path traversal attacks and spoof repositories via a crafted image in a (1) "docker load" operation or (2) "registry communications."

CVSS v2.0 (legacy)
6.4MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
6.4MEDIUMlow confidence
EG Risk
34
EG Risk 34/100CISA SSVC

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
Severity64% × 45%
Exploitation3% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Track* or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
2.5%
EPSS %ILE
84th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Track* or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

December 16, 2014

Last Modified

May 6, 2026

References (4)

Vendor Advisories for CVE-2014-9358(1)

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
redhatdocker-0:1.3.2-4.el72014-12-10redhat

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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
docker.io—
  • every version up to 1.3.3~dfsg1-1: fixed in 1.3.3~dfsg1-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
docker.io—
  • every version up to 1.3.3~dfsg1-1: fixed in 1.3.3~dfsg1-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
docker.io—
  • every version up to 1.3.3~dfsg1-1: fixed in 1.3.3~dfsg1-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
docker.io—
  • every version up to 1.3.3~dfsg1-1: fixed in 1.3.3~dfsg1-1
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/docker/docker—
  • every version up to 1.3.2: fixed in 1.3.2
—

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

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

Related CVEs(same product + same vendor)

Same vendor

1 shown

redhat:RHBA-2014:1977

Frequently asked(4)

What is CVE-2014-9358?
CVE-2014-9358 is a medium vulnerability published on December 16, 2014. Docker before 1.3.3 does not properly validate image IDs, which allows remote attackers to conduct path traversal attacks and spoof repositories via a crafted image in a (1) "docker load" operation or (2) "registry communications."
When was CVE-2014-9358 disclosed?
CVE-2014-9358 was first published on December 16, 2014, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2014-9358 actively exploited?
CVE-2014-9358 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.5% probability of exploitation in the next 30 days (84th percentile of EPSS-scored CVEs).
How do I remediate CVE-2014-9358?
A fix for CVE-2014-9358 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2014-9358 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-2014-9358

Explore →

Is Your Infrastructure Affected by CVE-2014-9358?

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

Book a Demo →Browse All CVEs