Skip to content
TrackCVE
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2020-8555

Kubernetes kube-controller-manager SSRF

Medium6.3EPSS 3.7%
Published
Updated
Reserved
Assigned by
kubernetes

Description

The Kubernetes kube-controller-manager in versions v1.0-1.14, versions prior to v1.15.12, v1.16.9, v1.17.5, and version v1.18.0 are vulnerable to a Server Side Request Forgery (SSRF) that allows certain authorized users to leak up to 500 bytes of arbitrary information from unprotected endpoints within the master's host network (such as link-local or loopback services).

Timeline

  1. ID reserved

    By kubernetes

  2. · 4 months later

    Published

  3. · 4 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2020-8555, by who scored it
Scored byCVSSScoreVector
kubernetesCNA (assigner)3.1Medium6.3CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N
NVDNVD · Modified3.1Medium6.3CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N
EPSS (exploitation in 30 days)
3.7% · top 10% of all CVEs (7 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 6.3.

Weakness

Affected products

  • Kubernetes · Kubernetes

    • affected 1.18.0
    • affected 1.1
    • affected 1.2
    • affected 1.3
    • affected 1.4
    • affected 1.5
    • affected 1.6
    • affected 1.7
    • affected 1.8
    • affected 1.9
    • affected 1.10
    • affected 1.11
    • affected 1.12
    • affected 1.13
    • affected 1.14
    • affected 1.15 – < 1.15.12
    • affected 1.16 – < 1.16.9
    • affected 1.17 – < 1.17.5

Affected packages

From reviewed advisories of the GitHub Advisory Database.

What to do

Workaround: Prior to upgrading, this vulnerability can be mitigated by adding endpoint protections on the master or restricting usage of the vulnerable volume types (for example by constraining usage with a PodSecurityPolicy or third-party admission controller such as Gatekeeper) and restricting StorageClass write permissions through RBAC.

References (6)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2020-8555 badge
[![CVE-2020-8555](https://trackcve.app/badge/CVE-2020-8555.svg)](https://trackcve.app/cve/CVE-2020-8555)

Record last updated .