How severe is CVE-2018-1000400?

CVE-2018-1000400 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-1000400 being actively exploited?

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

What products are affected by CVE-2018-1000400?

CVE-2018-1000400 affects Kubernetes Cri-o. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2018-1000400?

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-1000400 published?

CVE-2018-1000400 was published on 2018-05-18 and last updated on 2026-06-17.

CVE-2018-1000400

CVE-2018-1000400 is a high-severity vulnerability in Kubernetes Cri-o 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-269.

Key facts

Severity: High (CVSS 3.x base score 8.8)
CVSS v2: 6.5
EPSS exploit prediction: 2% (80th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-269
Affected product: Kubernetes Cri-o
Published: 2018-05-18
Last modified: 2026-06-17

Description

Kubernetes CRI-O version prior to 1.9 contains a Privilege Context Switching Error (CWE-270) vulnerability in the handling of ambient capabilities that can result in containers running with elevated privileges, allowing users abilities they should not have. This attack appears to be exploitable via container execution. This vulnerability appears to have been fixed in 1.9.

Frequently asked questions

What is CVE-2018-1000400?: Kubernetes CRI-O version prior to 1.9 contains a Privilege Context Switching Error (CWE-270) vulnerability in the handling of ambient capabilities that can result in containers running with elevated privileges, allowing users abilities they should not have. This attack appears to be exploitable via container execution. This vulnerability appears to have been fixed in 1.9.
How severe is CVE-2018-1000400?: CVE-2018-1000400 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-1000400 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (80th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2018-1000400?: CVE-2018-1000400 affects Kubernetes Cri-o. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2018-1000400?: 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-1000400 published?: CVE-2018-1000400 was published on 2018-05-18 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:kubernetes:cri-o:*:*:*:*:*:*:*:*

More vulnerabilities in Kubernetes Cri-o

CVE-2022-0811 — High (CVSS 8.8): A flaw was found in CRI-O in the way it set kernel options for a pod. This issue allows anyone with rights to deploy a…
CVE-2024-5154 — High (CVSS 8.1): A flaw was found in cri-o. A malicious container can create a symbolic link to arbitrary files on the host via…
CVE-2022-4318 — High (CVSS 7.8): A vulnerability was found in cri-o. This issue allows the addition of arbitrary lines into /etc/passwd by use of a…
CVE-2022-1708 — High (CVSS 7.5): A vulnerability was found in CRI-O that causes memory or disk space exhaustion on the node for anyone with access to…
CVE-2022-2995 — High (CVSS 7.1): Incorrect handling of the supplementary groups in the CRI-O container engine might lead to sensitive information…
CVE-2022-27652 — Medium (CVSS 5.3): A flaw was found in cri-o, where containers were incorrectly started with non-empty default permissions. A…

All CVEs affecting Kubernetes Cri-o →

Other CWE-269 (Improper Privilege Management) vulnerabilities

CVE-2026-31852 — Critical (CVSS 10.0): Jellyfin is an open-source media system. The code-quality.yml GitHub Actions workflow in jellyfin/jellyfin-ios is…
CVE-2025-20282 — Critical (CVSS 10.0): A vulnerability in an internal API of Cisco ISE and Cisco ISE-PIC could allow an unauthenticated, remote attacker to…
CVE-2025-0505 — Critical (CVSS 10.0): On Arista CloudVision systems (virtual or physical on-premise deployments), Zero Touch Provisioning can be used to gain…
CVE-2023-48418 — Critical (CVSS 10.0): In checkDebuggingDisallowed of DeviceVersionFragment.java, there is a possible way to access adb before SUW…
CVE-2023-48419 — Critical (CVSS 10.0): An attacker in the wifi vicinity of a target Google Home can spy on the victim, resulting in Elevation of Privilege
CVE-2023-31273 — Critical (CVSS 10.0): Protection mechanism failure in some Intel DCM software before version 5.2 may allow an unauthenticated user to…

Browse all CWE-269 (Improper Privilege Management) vulnerabilities →