NVD / CVE Program· CNA kubernetes

CVE-2020-8558: Kubernetes node setting allows for neighboring hosts to bypass localhost boundary

HighCVSS 8.8 · v3.1—Proof of concept Fix available

Noroxi assessment

Priority: Monitor (action score 36/100)

Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
Probability of exploitation in the next 30 days: 3.4% (FIRST EPSS); higher than 89% of all records.
Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: kubernetes (Debian:12) 1.18.5-1; k8s.io/kubernetes (Go) 1.17.7, 1.18.4, 1.16.11; govulncheck-vulndb (openSUSE:Tumbleweed) 0.0.20250807T150727-1.1.
Severity is disputed: the assigning authority (CNA) scores it 5.4, NVD 8.8.

Low priority for now. Upgrade to kubernetes (Debian:12) 1.18.5-1; k8s.io/kubernetes (Go) 1.17.7, 1.18.4, 1.16.11; govulncheck-vulndb (openSUSE:Tumbleweed) 0.0.20250807T150727-1.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

The Kubelet and kube-proxy components in versions 1.1.0-1.16.10, 1.17.0-1.17.6, and 1.18.0-1.18.3 were found to contain a security issue which allows adjacent hosts to reach TCP and UDP services bound to 127.0.0.1 running on the node or in the node's network namespace. Such a service is generally thought to be reachable only by other processes on the same host, but due to this defeect, could be reachable by other hosts on the same LAN as the node, or by containers running on the same node as the service.

Pre-auth

Published: Jul 27, 2020
Updated: Jun 16, 2026
EPSS: 3.4% · 89th percentile
CWE: CWE-420

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 35 / 40 · 8.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 1 / 30 · 3.4%

CNA vs NVD score

NVD: 8.8
CNA · kubernetes: 5.4; 3.4 point gap

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
Proof of concept exists, no weaponized module
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
kubernetes	kubernetes	cpe:2.3:a:kubernetes:kubernetes

Using kubernetes? Add it to your stack and be the first to know about CVEs like this one. (Kubernetes)

Versions reported by the vendor

Affected version ranges reported by the assigning authority (kubernetes). Independent of NVD's CPE analysis and usually ahead of it.

Kubernetes Kubernetes
- prior to 1.18.4, prior to 1.17.7, prior to 1.16.11, 1.15, 1.14, 1.13, 1.12, 1.11, 1.10, 1.9, 1.8, 1.7 … (+6)affected

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

kubernetes kubernetes1.1.0 and later · up to 1.16.10 inclusive
kubernetes kubernetes1.17.0 and later · up to 1.17.6 inclusive
kubernetes kubernetes1.18.0 and later · up to 1.18.3 inclusive

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

+11

Same product

kubernetes: all records

Other highest-scoring records for the same primary product.

CVE-2018-1002105In 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…
65This week
CVE-2019-11248Kubernetes kubelet exposes /debug/pprof info on healthz port
55Plan
CVE-2017-1002101In Kubernetes versions 1.3.x, 1.4.x, 1.5.x, 1.6.x and prior to versions 1.7.14, 1.8.9 and 1.9.4 containers using subpath volume mounts with…
42Plan

Published before and after this one in the same product

← EarlierCVE-2019-11252Jul 23, 2020 · Credential leakage when failing to mount
26Monitor
← EarlierCVE-2020-8557Jul 23, 2020 · Kubernetes node disk Denial of Service by writing to container /etc/hosts
22Monitor
Later →CVE-2020-8563Dec 7, 2020 · Secret leaks in logs for vSphere Provider kube-controller-manager
22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
debian:kubernetes	1.18.5-1 · Debian:12	Package registry (OSV)
Go:k8s.io/kubernetes	1.16.11	Package registry (OSV)
Go:k8s.io/kubernetes	1.17.7	Package registry (OSV)
Go:k8s.io/kubernetes	1.18.4	Package registry (OSV)
opensuse:govulncheck-vulndb	0.0.20250807T150727-1.1 · openSUSE:Tumbleweed	Package registry (OSV)
red hat:atomic-openshift	0:3.11.248-1.git.0.92ee8ac.el7 · Red Hat:openshift:3.11::el7	Package registry (OSV)
red hat:atomic-openshift-clients	0:3.11.248-1.git.0.92ee8ac.el7 · Red Hat:openshift:3.11::el7	Package registry (OSV)
red hat:atomic-openshift-clients-redistributable	0:3.11.248-1.git.0.92ee8ac.el7 · Red Hat:openshift:3.11::el7	Package registry (OSV)
red hat:atomic-openshift-docker-excluder	0:3.11.248-1.git.0.92ee8ac.el7 · Red Hat:openshift:3.11::el7	Package registry (OSV)
red hat:atomic-openshift-excluder	0:3.11.248-1.git.0.92ee8ac.el7 · Red Hat:openshift:3.11::el7	Package registry (OSV)
red hat:atomic-openshift-hyperkube	0:3.11.248-1.git.0.92ee8ac.el7 · Red Hat:openshift:3.11::el7	Package registry (OSV)
red hat:atomic-openshift-web-console	0:3.11.248-1.git.1.cc96c2d.el7 · Red Hat:openshift:3.11::el7	Package registry (OSV)
red hat:cri-o	0:1.11.16-0.10.dev.rhaos3.11.git1eee681.el7 · Red Hat:openshift:3.11::el7	Package registry (OSV)
red hat:cri-o-debuginfo	0:1.11.16-0.10.dev.rhaos3.11.git1eee681.el7 · Red Hat:openshift:3.11::el7	Package registry (OSV)
red hat:machine-config-daemon	0:4.5.0-202007012112.p0.git.2527.d12c3da.el8 · Red Hat:openshift:4.5::el8	Package registry (OSV)
red hat:openshift	0:4.5.0-202007012112.p0.git.0.582d7fc.el7 · Red Hat:openshift:4.5::el7	Package registry (OSV)
red hat:openshift-hyperkube	0:4.5.0-202007012112.p0.git.0.582d7fc.el7 · Red Hat:openshift:4.5::el7	Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

Proof-of-concept repository on GitHub ×2

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Proof-of-concept repository on GitHub	stars:43	2020-07-09
Proof-of-concept repository on GitHub	stars:3	2020-07-17

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

First PoCJul 9, 2020-19 d
PublishedJul 27, 2020
TodayNov 14, 2026+2300 d

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate.

Technical details

Attack conditions

Someone on the same network segment can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Adjacent
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-420 · Unprotected Alternate Channel

CVSS vector

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log (1)

Fix✗ → ✓Sep 28, 2026, 10:44 PM UTC

For records you follow, these changes also arrive as notifications. →

References

security.netapp.com/advisory/ntap-20200821-0001/

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records