How severe is CVE-2018-15514?

CVE-2018-15514 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2018-15514 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (83rd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2018-15514?

CVE-2018-15514 primarily affects Docker. In total, 104 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2018-15514?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2018-15514 published?

CVE-2018-15514 was published on 2018-09-01 and last updated on 2026-06-17.

CVE-2018-15514

CVE-2018-15514 is a high-severity vulnerability in Docker with a CVSS 3.x base score of 8.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-502.

Key facts

Severity: High (CVSS 3.x base score 8.8)
CVSS v2: 6.5
EPSS exploit prediction: 2% (83rd percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-502
Affected product: Docker
Published: 2018-09-01
Last modified: 2026-06-17

Description

HandleRequestAsync in Docker for Windows before 18.06.0-ce-rc3-win68 (edge) and before 18.06.0-ce-win72 (stable) deserialized requests over the \\.\pipe\dockerBackend named pipe without verifying the validity of the deserialized .NET objects. This would allow a malicious user in the "docker-users" group (who may not otherwise have administrator access) to escalate to administrator privileges.

Frequently asked questions

What is CVE-2018-15514?: HandleRequestAsync in Docker for Windows before 18.06.0-ce-rc3-win68 (edge) and before 18.06.0-ce-win72 (stable) deserialized requests over the \\.\pipe\dockerBackend named pipe without verifying the validity of the deserialized .NET objects. This would allow a malicious user in the "docker-users" group (who may not otherwise have administrator access) to escalate to administrator privileges.
How severe is CVE-2018-15514?: CVE-2018-15514 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2018-15514 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (83rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2018-15514?: CVE-2018-15514 primarily affects Docker. In total, 104 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2018-15514?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2018-15514 published?: CVE-2018-15514 was published on 2018-09-01 and last updated on 2026-06-17.

References

Affected products (104)

cpe:2.3:a:docker:docker:1.10.0.0-0:*:*:*:community:windows:*:*
cpe:2.3:a:docker:docker:1.10.1.42-1:*:*:*:community:windows:*:*
cpe:2.3:a:docker:docker:1.10.2.12:*:*:*:community:windows:*:*
cpe:2.3:a:docker:docker:1.10.2.14:*:*:*:community:windows:*:*
cpe:2.3:a:docker:docker:1.10.4.0:*:*:*:community:windows:*:*
cpe:2.3:a:docker:docker:1.10.6:*:*:*:community:windows:*:*
cpe:2.3:a:docker:docker:1.11.0:*:*:*:community:windows:*:*
cpe:2.3:a:docker:docker:1.11.0:beta10:*:*:community:windows:*:*
cpe:2.3:a:docker:docker:1.11.0:beta7:*:*:community:windows:*:*
cpe:2.3:a:docker:docker:1.11.0:beta8:*:*:community:windows:*:*
cpe:2.3:a:docker:docker:1.11.0:beta9:*:*:community:windows:*:*
cpe:2.3:a:docker:docker:1.11.1:beta11:*:*:community:windows:*:*
cpe:2.3:a:docker:docker:1.11.1:beta11b:*:*:community:windows:*:*
cpe:2.3:a:docker:docker:1.11.1:beta12:*:*:community:windows:*:*
cpe:2.3:a:docker:docker:1.11.1:beta13:*:*:community:windows:*:*
cpe:2.3:a:docker:docker:1.11.1:beta14:*:*:community:windows:*:*
cpe:2.3:a:docker:docker:1.11.2:beta15:*:*:community:windows:*:*
cpe:2.3:a:docker:docker:1.12.0:*:*:*:*:windows:*:*
cpe:2.3:a:docker:docker:1.12.0:beta21:*:*:community:windows:*:*
cpe:2.3:a:docker:docker:1.12.0:beta22:*:*:community:windows:*:*
cpe:2.3:a:docker:docker:1.12.0:rc2-beta16:*:*:community:windows:*:*
cpe:2.3:a:docker:docker:1.12.0:rc2-beta17:*:*:community:windows:*:*
cpe:2.3:a:docker:docker:1.12.0:rc3-beta18:*:*:community:windows:*:*
cpe:2.3:a:docker:docker:1.12.0:rc3-beta18.1:*:*:community:windows:*:*
cpe:2.3:a:docker:docker:1.12.0:rc4-beta19:*:*:community:windows:*:*
cpe:2.3:a:docker:docker:1.12.0:rc4-beta20:*:*:community:windows:*:*
cpe:2.3:a:docker:docker:1.12.1:*:*:*:*:windows:*:*
cpe:2.3:a:docker:docker:1.12.1:beta24:*:*:community:windows:*:*
cpe:2.3:a:docker:docker:1.12.1:beta25:*:*:community:windows:*:*
cpe:2.3:a:docker:docker:1.12.1:beta26:*:*:community:windows:*:*
cpe:2.3:a:docker:docker:1.12.1:beta29.1:*:*:community:windows:*:*
cpe:2.3:a:docker:docker:1.12.1:rc1-beta23:*:*:community:windows:*:*
cpe:2.3:a:docker:docker:1.12.2:beta29.2:*:*:community:windows:*:*
cpe:2.3:a:docker:docker:1.12.2:rc1-beta27:*:*:community:windows:*:*
cpe:2.3:a:docker:docker:1.12.2:rc3-beta28:*:*:community:windows:*:*
cpe:2.3:a:docker:docker:1.12.3:*:*:*:*:windows:*:*
cpe:2.3:a:docker:docker:1.12.3:beta29.3:*:*:community:windows:*:*
cpe:2.3:a:docker:docker:1.12.3:beta30:*:*:community:windows:*:*
cpe:2.3:a:docker:docker:1.12.3:rc1-beta29:*:*:community:windows:*:*
cpe:2.3:a:docker:docker:1.12.5:*:*:*:*:windows:*:*

More vulnerabilities in Docker

CVE-2014-9357 — Critical (CVSS 10.0): Docker 1.3.2 allows remote attackers to execute arbitrary code with root privileges via a crafted (1) image or (2)…
CVE-2014-0048 — Critical (CVSS 9.8): An issue was found in Docker before 1.6.0. Some programs and scripts in Docker are downloaded via HTTP and then…
CVE-2019-14271 — Critical (CVSS 9.8): In Docker 19.03.x before 19.03.1 linked against the GNU C Library (aka glibc), code injection can occur when the…
CVE-2020-14300 — High (CVSS 8.8): The docker packages version docker-1.13.1-108.git4ef4b30.el7 as released for Red Hat Enterprise Linux 7 Extras via…
CVE-2020-14298 — High (CVSS 8.8): The version of docker as released for Red Hat Enterprise Linux 7 Extras via RHBA-2020:0053 advisory included an…
CVE-2014-9356 — High (CVSS 8.6): Path traversal vulnerability in Docker before 1.3.3 allows remote attackers to write to arbitrary files and bypass a…

All CVEs affecting Docker →

Other CWE-502 (Deserialization of Untrusted Data) vulnerabilities

CVE-2026-41104 — Critical (CVSS 10.0): Deserialization of untrusted data in Microsoft Planetary Computer Pro allows an unauthorized attacker to disclose…
CVE-2026-43633 — Critical (CVSS 10.0): HestiaCP versions 1.9.0 through 1.9.4 contain a deserialization vulnerability in the web terminal component caused by a…
CVE-2026-33819 — Critical (CVSS 10.0): Deserialization of untrusted data in Microsoft Bing allows an unauthorized attacker to execute code over a network.
CVE-2026-20131 — Critical (CVSS 10.0): A vulnerability in the web-based management interface of Cisco Secure Firewall Management Center (FMC) Software could…
CVE-2026-25632 — Critical (CVSS 10.0): EPyT-Flow is a Python package designed for the easy generation of hydraulic and water quality scenario data of water…
CVE-2025-14931 — Critical (CVSS 10.0): Hugging Face smolagents Remote Python Executor Deserialization of Untrusted Data Remote Code Execution Vulnerability.…

Browse all CWE-502 (Deserialization of Untrusted Data) vulnerabilities →