How severe is CVE-2018-1002105?

CVE-2018-1002105 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2018-1002105?

CVE-2018-1002105 affects the following packages: github.com/kubernetes/kubernetes (Go), github.com/kubernetes/kubernetes (Go), github.com/kubernetes/kubernetes (Go). Ecosystems affected: Go.

How do I fix CVE-2018-1002105?

Update github.com/kubernetes/kubernetes to 1.10.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-1002105 is resolved across your whole dependency graph.

How do I detect CVE-2018-1002105 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/kubernetes/kubernetes, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2018-1002105 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2018-1002105 actively exploited in the wild?

Yes. There are 13 known exploit references for CVE-2018-1002105, including 2 documented proof-of-concept exploits on Exploit-DB and 7 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2018-1002105?

CVE-2018-1002105 has an EPSS (Exploit Prediction Scoring System) score of 87.0%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2018-1002105?

CVE-2018-1002105 is classified as CWE-388 (CWE-388). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2018-1002105 published, and has it been updated?

CVE-2018-1002105 was published on December 5, 2018 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

CRITICAL severity

CVE-2018-1002105 — kubernetes

CRITICALFix: kubernetes/kubernetes@2257c1e

CVE-2018-1002105 is a critical-severity (CVSS 9.8) CWE-388 vulnerability in github.com/kubernetes/kubernetes. 13 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for github.com/kubernetes/kubernetes — see the affected versions and patch details below.

Privilege Escalation in Kubernetes

Also known asGHSA-579h-mv94-g4gpGO-2022-0792

Published

Dec 5, 2018

Updated

Oct 24, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

13 known

Exploitation data as of Oct 31, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

87.0%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected

🐹github.com/kubernetes/kubernetes🐹github.com/kubernetes/kubernetes🐹github.com/kubernetes/kubernetes

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

In all Kubernetes versions prior to v1.10.11, v1.11.5, and v1.12.3, incorrect handling of error responses to proxied upgrade requests in the kube-apiserver allowed specially crafted requests to establish a connection through the Kubernetes API server to backend servers, then send arbitrary requests over the same connection directly to the backend, authenticated with the Kubernetes API server's TLS credentials used to establish the backend connection.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/kubernetes/kubernetes`	all versions	1.10.11`go get github.com/kubernetes/kubernetes@v1.10.11`
🐹Go	`github.com/kubernetes/kubernetes`	≥ 1.11.0&&< 1.11.5	1.11.5`go get github.com/kubernetes/kubernetes@v1.11.5`
🐹Go	`github.com/kubernetes/kubernetes`	≥ 1.12.0&&< 1.12.3	1.12.3`go get github.com/kubernetes/kubernetes@v1.12.3`

Affected Products

3 products · 14 configurations

Application

kuberneteskubernetes

≥ 1.12.0 && ≤ 1.12.2

1 version

1.9.12

Application

tridentnetapp

all

Application

openshift container platformredhat

8 versions

3.23.33.43.53.63.83.103.11

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-46052remotemultiple

Kubernetes - (Unauthenticated) Arbitrary Requests

by evict · Dec 10, 2018

Exploit-DB Source

EDB-46053remotemultiple

Kubernetes - (Authenticated) Arbitrary Requests

by evict · Dec 10, 2018

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/kubernetes/kubernetes, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/kubernetes/kubernetes to 1.10.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-1002105 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatCritical

In versions 3.6 and higher of OpenShift Container Platform, this vulnerability allows cluster-admin level access to any API hosted by an aggregated API server. This includes the ‘service catalog’ API which is installed by default in 3.7 and later. Cluster-admin level access to the service catalog allows creation of…

Workaround published by Red Hat

See the vulnerability article for mitigation procedures.

Source: Red Hat security advisory for CVE-2018-1002105 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat OpenShift Container Platform 3.10	`atomic-enterprise-service-catalog-1:3.10.72-1.git.1450.7d3f435.el7`	RHSA-2018:3549
Red Hat OpenShift Container Platform 3.11	`atomic-openshift-0:3.11.43-1.git.0.647ac05.el7`	RHSA-2018:3537
Red Hat OpenShift Container Platform 3.2	`atomic-openshift-0:3.2.1.34-2.git.20.6367d5d.el7`	RHSA-2018:3742
Red Hat OpenShift Container Platform 3.3	`atomic-openshift-0:3.3.1.46.45-1.git.0.2ce596e.el7`	RHSA-2018:3754
Red Hat OpenShift Container Platform 3.4	`atomic-openshift-0:3.4.1.44.57-1.git.0.a631031.el7`	RHSA-2018:3752
Red Hat OpenShift Container Platform 3.5	`atomic-openshift-0:3.5.5.31.80-1.git.0.c4a0780.el7`	RHSA-2018:3624
Red Hat OpenShift Container Platform 3.6	`atomic-openshift-0:3.6.173.0.140-1.git.0.9686d52.el7`	RHSA-2018:3598
Red Hat OpenShift Container Platform 3.7	`atomic-openshift-0:3.7.72-1.git.0.925b9cd.el7`	RHSA-2018:2906

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2018-1002105 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2018-1002105 — kubernetes

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2018-1002105 in your dependencies?