Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2018-1002105: Kubernetes kube-apiserver Proxy Request Privilege Escalation

Published Dec 5, 2018 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3
EPSS87.0%100th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendors
KubernetesRed HatNetApp
IdentifiersCVE-2018-1002105CWE-755

CVE-2018-1002105 is a privilege escalation vulnerability in Kubernetes kube-apiserver caused by incorrect handling of error responses to proxied protocol-upgrade requests. A specially crafted request can leave a connection to a backend server available for reuse, allowing an attacker to send arbitrary requests directly over that connection. These requests use the API server's backend TLS credentials rather than the attacker's privileges, bypassing the intended authorization boundary. Affected releases precede the branch-specific fixes in Kubernetes 1.10.11, 1.11.5, and 1.12.3.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Attackers can perform unauthorized operations against aggregated API servers or kubelet APIs with the privileges associated with the API server's backend TLS credentials. Depending on the accessible backend and its authorization configuration, exploitation can enable sensitive data access, command execution, privilege escalation, and potentially full cluster compromise.

Mitigation

If you can’t patch tonight, do this now.

Until patching is possible, suspend use of aggregated API servers, disable anonymous API-server requests, and remove unnecessary pod exec, attach, and port-forward permissions. These measures reduce available exploitation paths but may disrupt cluster operations and are not substitutes for upgrading.

Remediation

Patch, then assume compromise.

Upgrade to a patched Kubernetes release. Historical fixes were released in versions 1.10.11, 1.11.5, 1.12.3, and 1.13.0-rc.1; deployments should now use a supported release incorporating those fixes. For Kubernetes distributions, apply the vendor's corresponding security update. AWS reported that its Amazon EKS control-plane fleet was patched and required no customer action for that update.

Public exploits

Exploits

1 exploit validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit; 2 not yet analyzed, such as Exploit-DB entries.

View more in app →
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
KubernetesKubernetesapplication
NetAppTridentapplication
Red HatOpenshift Container Platformapplication
FAQ

Frequently asked questions

Is CVE-2018-1002105 exploited in the wild?
As of Oct 23, 2026, Mallory has no reports of CVE-2018-1002105 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2018-1002105?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2018-1002105, the earliest disclosed Dec 6, 2018.
Is there a patch for CVE-2018-1002105?
Upgrade to a patched Kubernetes release. Historical fixes were released in versions 1.10.11, 1.11.5, 1.12.3, and 1.13.0-rc.1; deployments should now use a supported release incorporating those fixes.
What products are affected by CVE-2018-1002105?
Kubernetes, Red Hat Openshift Container Platform, and NetApp Trident.
How severe is CVE-2018-1002105?
CVE-2018-1002105 has a CVSS v3 score of 9.8 (Critical) and an EPSS score of 87.0% (100th percentile) as of Oct 23, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware1Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.