How severe is CVE-2018-1002101?

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

Is CVE-2018-1002101 being actively exploited?

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

What products are affected by CVE-2018-1002101?

CVE-2018-1002101 affects Kubernetes. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2018-1002101?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2018-1002101 published?

CVE-2018-1002101 was published on 2018-12-05 and last updated on 2026-06-17.

CVE-2018-1002101

CVE-2018-1002101 is a medium-severity vulnerability in Kubernetes with a CVSS 3.x base score of 5.9. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 3.x base score 5.9)
CVSS v2: 7.5
EPSS exploit prediction: 4% (90th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Kubernetes
Published: 2018-12-05
Last modified: 2026-06-17

Description

In Kubernetes versions 1.9.0-1.9.9, 1.10.0-1.10.5, and 1.11.0-1.11.1, user input was handled insecurely while setting up volume mounts on Windows nodes, which could lead to command line argument injection.

Frequently asked questions

What is CVE-2018-1002101?: In Kubernetes versions 1.9.0-1.9.9, 1.10.0-1.10.5, and 1.11.0-1.11.1, user input was handled insecurely while setting up volume mounts on Windows nodes, which could lead to command line argument injection.
How severe is CVE-2018-1002101?: CVE-2018-1002101 has a CVSS 3.x base score of 5.9, rated medium severity. It is exploitable over network with high attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2018-1002101 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 4% (90th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2018-1002101?: CVE-2018-1002101 affects Kubernetes. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2018-1002101?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2018-1002101 published?: CVE-2018-1002101 was published on 2018-12-05 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:kubernetes:kubernetes:*:*:*:*:*:*:*:*

More vulnerabilities in Kubernetes

CVE-2018-1002105 — Critical (CVSS 9.8): In all Kubernetes versions prior to v1.10.11, v1.11.5, and v1.12.3, incorrect handling of error responses to proxied…
CVE-2017-1000056 — Critical (CVSS 9.8): Kubernetes version 1.5.0-1.5.4 is vulnerable to a privilege escalation in the PodSecurityPolicy admission plugin…
CVE-2016-1906 — Critical (CVSS 9.8): Openshift allows remote attackers to gain privileges by updating a build configuration that was created with an allowed…
CVE-2023-3955 — High (CVSS 8.8): A security issue was discovered in Kubernetes where a user that can create pods on Windows nodes may be able to…
CVE-2023-3676 — High (CVSS 8.8): A security issue was discovered in Kubernetes where a user that can create pods on Windows nodes may be able to…
CVE-2021-25741 — High (CVSS 8.8): A security issue was discovered in Kubernetes where a user may be able to create a container with subpath volume mounts…

All CVEs affecting Kubernetes →