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.

Published: 2018-05-18 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2018-1000400 is rated Moderate Risk (64.1/100): CVSS High severity, with medium exploitation likelihood (EPSS 2.11%). EPSS rose +1.18% over the last day, indicating growing attacker interest. Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2018-1000400

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.93% 2.11% +1.18%
2 2025-03-30 2.62% 0.93% -1.69%
3 2025-03-29 — 2.62% —

Full EPSS history (11 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2018-1000400

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.8 3.0 HIGH
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 [email protected]
6.5 2.0 MEDIUM
AV:N/AC:L/Au:S/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:S)
A single authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.0 6.4 [email protected]

Weakness enumeration for CVE-2018-1000400

OS Trackers for CVE-2018-1000400

vendor priority summary link
redhat medium — https://access.redhat.com/security/cve/CVE-2018-1000400
ubuntu medium CVE-2018-1000400 medium priority: Ubuntu including 1 source packages (cri-o), 5 status rows across 5 suites (focal, jammy, noble, oracular, upstream): DNE 4, needs-triage 1. https://ubuntu.com/security/CVE-2018-1000400

Affected software / configurations for CVE-2018-1000400

Vendor Product Version Raw CPE
kubernetes cri-o < 1.9.0 cpe:2.3:a:kubernetes:cri-o:*:*:*:*:*:*:*:*

References for CVE-2018-1000400

URL Tags
http://www.securityfocus.com/bid/104262 Third Party Advisory VDB Entry
https://github.com/kubernetes-incubator/cri-o/pull/1558/files Patch Third Party Advisory
cvelogic Threat Intelligence