Kubernetes API Server denial of service vulnerability from malicious YAML payloads
Noroxi assessment
Priority: Monitor (action score 27/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 3.1% (FIRST EPSS); higher than 87.8% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: kubernetes (Debian:12) 1.17.4-1; gopkg.in/yaml.v2 (Go) 2.2.8; etcd (openSUSE:Tumbleweed) 3.5.2-1.1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to kubernetes (Debian:12) 1.17.4-1; gopkg.in/yaml.v2 (Go) 2.2.8; etcd (openSUSE:Tumbleweed) 3.5.2-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 Kubernetes API Server component in versions 1.1-1.14, and versions prior to 1.15.10, 1.16.7 and 1.17.3 allows an authorized user who sends malicious YAML payloads to cause the kube-apiserver to consume excessive CPU cycles while parsing YAML.
- Published
- Apr 1, 2020
- Updated
- Jun 16, 2026
- EPSS
- 3.1% · 87th percentile
- CWE
- CWE-1050
Report tools
Action score
27
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.1%
CNA vs NVD score
- NVD
- 6.5
- CNA · kubernetes
- 6.5
- agree
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
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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)
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- kubernetes kubernetesbefore 1.15.10
- kubernetes kubernetes1.16.0 and later · before 1.16.7
- kubernetes kubernetes1.17.0 and later · before 1.17.3
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.15.10, prior to 1.16.7, prior to 1.17.3, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 1.7, 1.8, 1.9 … (+5)affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | kubernetes | before 1.17.4-1 | 1.17.4-1 |
| Go | github.com/go-yaml/yaml | from 0 | — |
| Go | github.com/go-yaml/yaml | up to and including 2.1.0 | — |
| Go | gopkg.in/yaml.v2 | before 2.2.8 | 2.2.8 |
| openSUSE:Tumbleweed | etcd | before 3.5.2-1.1 | 3.5.2-1.1 |
| Red Hat:openshift:3.11::el7 | atomic-openshift | before 0:3.11.232-1.git.0.a5bc32f.el7 | 0:3.11.232-1.git.0.a5bc32f.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-clients | before 0:3.11.232-1.git.0.a5bc32f.el7 | 0:3.11.232-1.git.0.a5bc32f.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-clients-redistributable | before 0:3.11.232-1.git.0.a5bc32f.el7 | 0:3.11.232-1.git.0.a5bc32f.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-docker-excluder | before 0:3.11.232-1.git.0.a5bc32f.el7 | 0:3.11.232-1.git.0.a5bc32f.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-excluder | before 0:3.11.232-1.git.0.a5bc32f.el7 | 0:3.11.232-1.git.0.a5bc32f.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-hyperkube | before 0:3.11.232-1.git.0.a5bc32f.el7 | 0:3.11.232-1.git.0.a5bc32f.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-hypershift | before 0:3.11.232-1.git.0.a5bc32f.el7 | 0:3.11.232-1.git.0.a5bc32f.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-master | before 0:3.11.232-1.git.0.a5bc32f.el7 | 0:3.11.232-1.git.0.a5bc32f.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-node | before 0:3.11.232-1.git.0.a5bc32f.el7 | 0:3.11.232-1.git.0.a5bc32f.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-pod | before 0:3.11.232-1.git.0.a5bc32f.el7 | 0:3.11.232-1.git.0.a5bc32f.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-sdn-ovs | before 0:3.11.232-1.git.0.a5bc32f.el7 | 0:3.11.232-1.git.0.a5bc32f.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-template-service-broker | before 0:3.11.232-1.git.0.a5bc32f.el7 | 0:3.11.232-1.git.0.a5bc32f.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-tests | before 0:3.11.232-1.git.0.a5bc32f.el7 | 0:3.11.232-1.git.0.a5bc32f.el7 |
| Red Hat:openshift:4.5::el7 | openshift | before 0:4.5.0-202007012112.p0.git.0.582d7fc.el7 | 0:4.5.0-202007012112.p0.git.0.582d7fc.el7 |
| Red Hat:openshift:4.5::el7 | openshift-hyperkube | before 0:4.5.0-202007012112.p0.git.0.582d7fc.el7 | 0:4.5.0-202007012112.p0.git.0.582d7fc.el7 |
| Red Hat:openshift:4.5::el8 | machine-config-daemon | before 0:4.5.0-202007012112.p0.git.2527.d12c3da.el8 | 0:4.5.0-202007012112.p0.git.2527.d12c3da.el8 |
| Red Hat:openshift:4.5::el8 | openshift | before 0:4.5.0-202007012112.p0.git.0.582d7fc.el8 | 0:4.5.0-202007012112.p0.git.0.582d7fc.el8 |
| Red Hat:openshift:4.5::el8 | openshift-hyperkube | before 0:4.5.0-202007012112.p0.git.0.582d7fc.el8 | 0:4.5.0-202007012112.p0.git.0.582d7fc.el8 |
| SUSE:Package Hub 15 SP6 | etcd | before 3.5.12-bp156.4.3.1 | 3.5.12-bp156.4.3.1 |
+1
Same product
kubernetes: all recordsOther 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 the65This week
- CVE-2019-11248Kubernetes kubelet exposes /debug/pprof info on healthz port55Plan
- 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-2020-8551Mar 27, 2020 · Kubernetes kubelet denial of service26Monitor
- ← EarlierCVE-2020-8552Mar 27, 2020 · Kubernetes API server denial of service18Monitor
- Later →CVE-2020-8555Jun 5, 2020 · Kubernetes kube-controller-manager SSRF26Monitor
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.17.4-1 · Debian:12 | Package registry (OSV) |
| Go:gopkg.in/yaml.v2 | 2.2.8 | Package registry (OSV) |
| opensuse:etcd | 3.5.12-bp156.4.3.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:etcd | 3.5.2-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:atomic-openshift | 0:3.11.232-1.git.0.a5bc32f.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-clients | 0:3.11.232-1.git.0.a5bc32f.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-clients-redistributable | 0:3.11.232-1.git.0.a5bc32f.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-docker-excluder | 0:3.11.232-1.git.0.a5bc32f.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-excluder | 0:3.11.232-1.git.0.a5bc32f.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-hyperkube | 0:3.11.232-1.git.0.a5bc32f.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-hypershift | 0:3.11.232-1.git.0.a5bc32f.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-master | 0:3.11.232-1.git.0.a5bc32f.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-node | 0:3.11.232-1.git.0.a5bc32f.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) |
| suse:etcd | 3.5.12-bp156.4.3.1 · SUSE:Package Hub 15 SP6 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
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.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Mike DaneseGoogle
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-20-621 · Aug 19, 2020(IBM Ürünleri Güvenlik Güncellemesi)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-1050 · Excessive Platform Resource Consumption within a LoopCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.