CVE-2020-8553

CVE-2020-8553 is a medium-severity vulnerability in Kubernetes Ingress-nginx with a CVSS 3.x base score of 5.9. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-610.

Key facts

Description

The Kubernetes ingress-nginx component prior to version 0.28.0 allows a user with the ability to create namespaces and to read and create ingress objects to overwrite the password file of another ingress which uses nginx.ingress.kubernetes.io/auth-type: basic and which has a hyphenated namespace or secret name.

Frequently asked questions

What is CVE-2020-8553?
The Kubernetes ingress-nginx component prior to version 0.28.0 allows a user with the ability to create namespaces and to read and create ingress objects to overwrite the password file of another ingress which uses nginx.ingress.kubernetes.io/auth-type: basic and which has a hyphenated namespace or secret name.
How severe is CVE-2020-8553?
CVE-2020-8553 has a CVSS 3.x base score of 5.9, rated medium severity. It is exploitable over network with high attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2020-8553 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (55th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-8553?
CVE-2020-8553 affects Kubernetes Ingress-nginx. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2020-8553?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2020-8553 published?
CVE-2020-8553 was published on 2020-07-29 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Kubernetes Ingress-nginx

All CVEs affecting Kubernetes Ingress-nginx →

Other CWE-610 vulnerabilities

Browse all CWE-610 vulnerabilities →