# CVE-2020-8561: Webhook redirect in kube-apiserver

> Attackers controlling webhook responses can redirect API server requests to private networks, potentially exposing sensitive data in logs if verbose logging is enabled.

- **Severity:** Medium 4.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Sep 2021
- **Updated:** 1 Jun 2026
- **Also known as:** AZL-89315, DEBIAN-CVE-2020-8561, GHSA-74j8-88mm-7496, openSUSE-SU-2026:11388-1, openSUSE-SU-2026:11389-1, openSUSE-SU-2026:11390-1, openSUSE-SU-2026:11391-1

## What is CVE-2020-8561?

CVE-2020-8561 is a medium-severity server-side request forgery vulnerability in Kubernetes Kubernetes, published on 20 Sep 2021. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A security issue was discovered in Kubernetes where actors that control the responses of MutatingWebhookConfiguration or ValidatingWebhookConfiguration requests are able to redirect kube-apiserver requests to private networks of the apiserver. If that user can view kube-apiserver logs when the log level is set to 10, they can view the redirected responses and headers in the logs.

Weakness: CWE-610 (Externally Controlled Reference to a Resource in Another Sphere), CWE-441 (Unintended Proxy or Intermediary)

## Which versions are affected by CVE-2020-8561?

2 open source packages ship an affected version, including k8s.io/kubernetes. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `k8s.io/kubernetes` | Go | All versions to 1.22.2 | None |
| `k8s.io/kubernetes` | Go | All versions to 1.22.2 | None |
| `kubernetes1.33` | openSUSE:Tumbleweed | All versions | 1.33.13-2.1 |
| `kubernetes1.34` | openSUSE:Tumbleweed | All versions | 1.34.10-1.1 |
| `kubernetes1.35` | openSUSE:Tumbleweed | All versions | 1.35.7-1.1 |
| `kubernetes1.36` | openSUSE:Tumbleweed | All versions | 1.36.3-1.1 |

Products: Kubernetes Kubernetes.

## How do I fix CVE-2020-8561?

Upgrade to a fixed version.

## Is CVE-2020-8561 being exploited?

There is no known exploitation of CVE-2020-8561 in the wild and no public exploit code.

## Other vulnerabilities in Kubernetes Kubernetes

- [CVE-2018-1002105](https://insights.sbomify.com/CVE-2018-1002105/): Privilege Escalation in Kubernetes (critical 9.8)
- [CVE-2017-1000056](https://insights.sbomify.com/CVE-2017-1000056/): Kubernetes Privilege Escalation (critical 9.8)
- [CVE-2016-1906](https://insights.sbomify.com/CVE-2016-1906/): Authorization bypass in Openshift (critical 9.8)
- [CVE-2023-3676](https://insights.sbomify.com/CVE-2023-3676/): Kubernetes - Windows nodes - Insufficient input sanitization leads to privilege escalation (high 8.8)
- [CVE-2023-3955](https://insights.sbomify.com/CVE-2023-3955/): Kubernetes - Windows nodes - Insufficient input sanitization leads to privilege escalation (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-8561 and fix it if it is affected.

What it is: CVE-2020-8561 is a medium-severity server-side request forgery vulnerability in Kubernetes Kubernetes, published on 20 Sep 2021. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-8561 in the wild and no public exploit code.

Affected packages and fixed versions:
- k8s.io/kubernetes (Go): affected all versions up to 1.22.2; no fix listed
- k8s.io/kubernetes (Go): affected all versions up to 1.22.2; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-8561/ (Markdown: https://insights.sbomify.com/CVE-2020-8561/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-8561
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-8561
- OSV: https://osv.dev/vulnerability/CVE-2020-8561

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-8561/
Summaries are generated and may contain mistakes; the official description above is the record.