CVE-2018-1002105

CRITICALNVD 9.89.8
EchelonGraph scoreHIGH confidence

Score elevated to 9.8 because EPSS predicts 90% probability of exploitation within the next 30 days (top 0.4% of all CVEs). NVD baseline CVSS 9.8 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Elevated
9.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 87%
CISA-KEV: Not listedEPSS: 87%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8(high)
EPSS
99.7%
KEV
Not listed

Published

December 5, 2018

Last Modified

November 21, 2024

Advisory Details (9)

Auto-updated Jun 6, 2026
Patch available. Sources: redhat.
generic

oss-security - Re: linux-distros membership application - Microsoft

http://www.openwall.com/lists/oss-security/2019/07/06/4
generic

oss-security - Re: linux-distros membership application - Microsoft

http://www.openwall.com/lists/oss-security/2019/07/06/3
generic

oss-security - Re: linux-distros membership application - Microsoft

http://www.openwall.com/lists/oss-security/2019/06/28/2

Patch Availability(10)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/kubernetes/kubernetes1.12.3

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(10)

Data Freshness Timeline

(refreshed 4× in last 7d / 17× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 14:04 UTCEPSS rescore
  2. 2026-07-21 02:17 UTCOSV refresh
  3. 2026-07-20 17:04 UTCEPSS rescore
  4. 2026-07-20 17:04 UTCEPSS rescore
  5. 2026-07-15 16:55 UTCEPSS rescore
  6. 2026-07-15 16:54 UTCEPSS rescore
  7. 2026-07-13 22:26 UTCEPSS rescore
  8. 2026-07-13 22:26 UTCEPSS rescore
  9. 2026-07-11 08:24 UTCEPSS rescore
  10. 2026-07-08 15:11 UTCEPSS rescore
  11. 2026-07-04 06:28 UTCEPSS rescore
  12. 2026-07-04 06:28 UTCEPSS rescore
  13. 2026-07-03 21:26 UTCOSV refresh
  14. 2026-07-01 15:03 UTCEPSS rescore
  15. 2026-06-25 13:47 UTCEPSS rescore
  16. 2026-06-23 21:30 UTCEPSS rescore
  17. 2026-06-23 21:30 UTCEPSS rescore
  18. 2026-06-18 17:50 UTCEPSS rescore
  19. 2026-06-17 17:50 UTCEPSS rescore
  20. 2026-06-15 17:45 UTCEPSS rescore
  21. 2026-06-15 09:13 UTCOSV refresh
  22. 2026-06-12 23:09 UTCEPSS rescore
  23. 2026-06-12 23:09 UTCEPSS rescore
  24. 2026-06-10 22:15 UTCEPSS rescore
  25. 2026-06-10 13:19 UTCEPSS rescore
Show 21 more
  1. 2026-06-07 15:22 UTCEPSS rescore
  2. 2026-06-07 15:22 UTCEPSS rescore
  3. 2026-06-06 13:45 UTCEPSS rescore
  4. 2026-06-06 13:45 UTCEPSS rescore
  5. 2026-06-05 22:44 UTCEPSS rescore
  6. 2026-06-05 22:44 UTCEPSS rescore
  7. 2026-06-05 06:08 UTCEPSS rescore
  8. 2026-06-05 06:08 UTCEPSS rescore
  9. 2026-06-02 20:11 UTCEPSS rescore
  10. 2026-06-02 20:11 UTCEPSS rescore
  11. 2026-05-31 00:14 UTCEPSS rescore
  12. 2026-05-31 00:14 UTCEPSS rescore
  13. 2026-05-28 13:42 UTCEPSS rescore
  14. 2026-05-28 13:42 UTCEPSS rescore
  15. 2026-05-28 00:35 UTCEG score recompute
  16. 2026-05-28 00:35 UTCVendor advisory
  17. 2026-05-27 14:35 UTCOSV refresh
  18. 2026-05-27 13:38 UTCEPSS rescore
  19. 2026-05-27 13:38 UTCEPSS rescore
  20. 2026-05-26 07:17 UTCEPSS rescore
  21. 2026-05-26 07:17 UTCEPSS rescore

Publicly available exploits

(5 references)

Working exploit code is in the public domain (3 GitHub PoCs) (2 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-46053
    First seen Dec 10, 2018

    Kubernetes - (Authenticated) Arbitrary Requests

    Open source ↗
  • Exploit-DBEDB-46052
    First seen Dec 10, 2018

    Kubernetes - (Unauthenticated) Arbitrary Requests

    Open source ↗
  • GitHub PoCimlzw/Kubernetes-1.12.3-all-auto-install
    First seen Dec 10, 2018

    个人整理的Centos7.x + Kubernetes-1.12.3 + Dashboard-1.8.3 无 CVE-2018-1002105 漏洞的master节点全自动快速一键安装部署文件,适用于测试环境,生产环境的快速安装部署

    Open source ↗
  • GitHub PoCevict/poc_CVE-2018-1002105
    First seen Dec 6, 2018

    PoC for CVE-2018-1002105.

    Open source ↗
  • GitHub PoCgravitational/cve-2018-1002105
    First seen Dec 5, 2018

    Test utility for cve-2018-1002105

    Open source ↗

Frequently asked(5)

What is CVE-2018-1002105?
CVE-2018-1002105 is a critical vulnerability published on December 5, 2018. 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…
When was CVE-2018-1002105 disclosed?
CVE-2018-1002105 was first published in the National Vulnerability Database on December 5, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-1002105 actively exploited?
CVE-2018-1002105 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2018-1002105?
CVE-2018-1002105 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2018-1002105?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-1002105, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2018-1002105

Explore →

Is Your Infrastructure Affected by CVE-2018-1002105?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.