Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.3

Server Side Request Forgery (SSRF) in Kubernetes

CVE-2020-8555GHSA-x6mj-w4jf-jmgw

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (k8s.io/kubernetes 1.18.1, 1.17.4, 1.16.9, 1.15.12), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go k8s.io/kubernetes

    Affected
    >= 1.18.0, < 1.18.1>= 1.17.0, < 1.17.4>= 1.16.0, < 1.16.9< 1.15.12
    Fixed in
    1.15.12, 1.16.9, 1.17.4, 1.18.1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.3 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N
EPSS
  • CVE-2020-8555: 3.68% estimated exploitation activity in the next 30 days; percentile 89.69 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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).

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-x6mj-w4jf-jmgw

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-8555

Advisory: Server Side Request Forgery (SSRF) in Kubernetes
IDs: CVE-2020-8555, GHSA-x6mj-w4jf-jmgw
Record: https://patchnext.com/advisories/cve-2020-8555 (revision 1, source checked 26 Oct 2026, 14:59 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: k8s.io/kubernetes 1.18.1, 1.17.4, 1.16.9, 1.15.12. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go k8s.io/kubernetes: affected >= 1.18.0, < 1.18.1; >= 1.17.0, < 1.17.4; >= 1.16.0, < 1.16.9; < 1.15.12; fixed in 1.15.12, 1.16.9, 1.17.4, 1.18.1

## Suggested inspection (read-only)
- Go k8s.io/kubernetes: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on k8s.io/kubernetes.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-x6mj-w4jf-jmgw (GitHub-reviewed advisory GHSA-x6mj-w4jf-jmgw lists affected ranges: Go k8s.io/kubernetes >=1.18.0 =1.17.0 =1.16.0 =0 <1.15.12)

Commands are suggestions: review each one before running it.

Loading voting…