CVE-2018-1002105: In all Kubernetes versions prior to v1.10.11, v1.11.5, and v1.12.3, incorrect handling of error responses to p

Q: How do I fix CVE-2018-1002105?

kubernetes: upgrade to newer than 1.12.2; openshift container platform: downgrade or apply the listed mitigation; trident: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Q: Is CVE-2018-1002105 being exploited?

CVE-2018-1002105 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2018-1002105 affect?

CVE-2018-1002105 affects kubernetes, openshift container platform, trident. Severity is 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 upgrade requests in the kube-apiserver allowed specially crafted requests to establish a connection through the Kubernetes

Q: How urgent is CVE-2018-1002105?

Priority 74/100. Critical severity; EPSS top 1%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action; On your watchlist

This week

CRITICAL 9.8REMOTEWATCHLISTUPGRADEDOWNGRADEMITIGATE

CVE-2018-1002105 is a critical-severity flaw (CVSS 9.8) affecting kubernetes, openshift container platform, trident. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 connect

Why this priority

Critical severity
EPSS top 1%: very likely to be exploited
Public exploit reference
Remotely exploitable, no login, no user action
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	87.0% (top 1%)
CISA exploited list	No
Weakness	CWE-388
Published	2018-12-05
Last modified	2026-06-17

Publisher (CNA): Kubernetes · Vendor: kubernetes · netapp · redhat

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-12-05 21:29 UTCPublished CVE record published
2026-06-17 01:33 UTCUpdated Record last modified

kubernetes kubernetes UPGRADE

Affected: >= 1.0.0 and <= 1.9.11 · >= 1.10.0 and <= 1.10.10 · >= 1.11.0 and <= 1.11.4 · >= 1.12.0 and <= 1.12.2 · 1.9.12 beta0

Fixed in: newer than 1.12.2

Safe to downgrade to: a release before 1.0.0

1. Check installed version

apt-cache policy kubernetes || rpm -q kubernetes || kubernetes --version

2. UPGRADE to newer than 1.12.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade kubernetes

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade kubernetes

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 1.0.0 (Debian / Ubuntu)

apt-cache madison kubernetes sudo apt install kubernetes=<VERSION_BEFORE_1.0.0> sudo apt-mark hold kubernetes

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list kubernetes sudo dnf downgrade kubernetes-<VERSION_BEFORE_1.0.0> sudo dnf versionlock add kubernetes

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

redhat openshift container platform DOWNGRADE

Affected: 3.2 · 3.3 · 3.4 · 3.5 · 3.6 · 3.8 · 3.10 · 3.11

Fixed in: no fixed release known

Safe to downgrade to: a release before 3.2

1. Check installed version

apt-cache policy openshift-container-platform || rpm -q openshift-container-platform || openshift-container-platform --version

2. No fixed release: DOWNGRADE to a release before 3.2 (Debian / Ubuntu)

apt-cache madison openshift-container-platform sudo apt install openshift-container-platform=<VERSION_BEFORE_3.2> sudo apt-mark hold openshift-container-platform

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list openshift-container-platform sudo dnf downgrade openshift-container-platform-<VERSION_BEFORE_3.2> sudo dnf versionlock add openshift-container-platform

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

netapp trident MITIGATE

Affected: all versions

Fixed in: no fixed release known

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy trident || rpm -q trident || trident --version

No fixed or unaffected release known

Apply the vendor mitigation from the advisory, disable the affected feature, or restrict network access.

Exact fixes by distribution

A distro patch exists: prefer upgrading over downgrading.

Go · github.com/kubernetes/kubernetes · FIXED · 1.10.11 · vulnerable: < 1.10.11 · source

go get github.com/kubernetes/kubernetes@v1.10.11 go list -m github.com/kubernetes/kubernetes

Fedora 46 · copyparty · FIXED · 1.20.26-1.fc46 · FEDORA-2026-8fbe18458e · source

sudo dnf upgrade --advisory=FEDORA-2026-8fbe18458e

Fedora ELN · man-pages · FIXED · 6.20-1.eln159 · FEDORA-2026-f1f5fb11b4 · source

sudo dnf upgrade --advisory=FEDORA-2026-f1f5fb11b4

Ubuntu 20.04 · kubernetes · NOT AFFECTED

Ubuntu 22.04 · kubernetes · NOT AFFECTED

Ubuntu 24.04 · kubernetes · NOT AFFECTED

Debian 12 · kubernetes · FIXED · 1.17.4-1

sudo apt update && sudo apt install --only-upgrade kubernetes dpkg --compare-versions "$(dpkg-query -W -f='${Version}' kubernetes)" ge "1.17.4-1" && echo PATCHED || echo STILL-VULNERABLE

Debian 13 · kubernetes · FIXED · 1.17.4-1

sudo apt update && sudo apt install --only-upgrade kubernetes dpkg --compare-versions "$(dpkg-query -W -f='${Version}' kubernetes)" ge "1.17.4-1" && echo PATCHED || echo STILL-VULNERABLE

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

GitHub PoC: evict/poc_CVE-2018-1002105 (223 stars)
GitHub PoC: gravitational/cve-2018-1002105 (191 stars)
GitHub PoC: imlzw/Kubernetes-1.12.3-all-auto-install (4 stars)
Write-up: www.exploit-db.com/exploits/46052/
Write-up: www.exploit-db.com/exploits/46053/
GitHub PoC: bgeesaman/cve-2018-1002105
Exploit-DB: Kubernetes - (Authenticated) Arbitrary Requests
Exploit-DB: Kubernetes - (Unauthenticated) Arbitrary Requests

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2018-1002105?

kubernetes: upgrade to newer than 1.12.2; openshift container platform: downgrade or apply the listed mitigation; trident: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2018-1002105 being exploited?

CVE-2018-1002105 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2018-1002105 affect?

CVE-2018-1002105 affects kubernetes, openshift container platform, trident. Severity is 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 upgrade requests in the kube-apiserver allowed specially crafted requests to establish a connection through the Kubernetes

How urgent is CVE-2018-1002105?

Priority 74/100. Critical severity; EPSS top 1%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action; On your watchlist

Software pages

Kubernetes vulnerabilities · Red Hat OpenShift vulnerabilities

Related CVEs

CVE-2023-5528 HIGH 7.2 UPGRADE MITIGATE A security issue was discovered in Kubernetes where a user that can create pods and persistent volumes on Wind
CVE-2023-3955 HIGH 8.8 UPGRADE A security issue was discovered in Kubernetes where a user that can create pods on Windows nodes may be able
CVE-2023-3676 HIGH 8.8 UPGRADE A security issue was discovered in Kubernetes where a user that can create pods on Windows nodes may be able
CVE-2023-30513 HIGH 7.5 UPGRADE Jenkins Kubernetes Plugin 3909.v1f2c633e8590 and earlier does not properly mask (i.e., replace with asterisks)
CVE-2023-2728 MEDIUM 6.5 UPGRADE Users may be able to launch containers that bypass the mountable secrets policy enforced by the ServiceAccount

References

← Back to latest CVEs