CVE-2020-8561MediumMicrosoft CVSS 4.1CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N

Microsoft security update for CVE-2020-8561

Published
October 1, 2025
Last Modified
—

🔗 CVE IDs covered (1)

📋 Microsoft's advisory

EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2020-8561. This page also shows what EchelonGraph holds for CVE-2020-8561, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.

🎯 Affected products7

  • azl3 kubernetes 1.30.10-25 on Azure Linux 3.0
  • azl3 kubernetes 1.30.10-27 on Azure Linux 3.0
  • azl3 kubernetes 1.30.10-29 on Azure Linux 3.0
  • azl3 kubernetes 1.30.10-30 on Azure Linux 3.0
  • azl3 kubernetes 1.30.10-32 on Azure Linux 3.0
  • azl3 kubernetes 1.30.10-33 on Azure Linux 3.0
  • cm1 kubernetes 1.22.6-1 on CBL Mariner 1.0

✅ Updates Microsoft lists: 3 updates

3 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.

KB articleUpdateFixed build
—Security Update—
—Security Update—
—Security Update1.22.6-1

🧭 EchelonGraph on CVE-2020-8561

EchelonGraph score
4.1 MEDIUM
CISA KEV
Not listed
Fix status
A fix is available — apply it.

Description from the CVE record (CVE.org), as published by its numbering authority

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.

Published by Kubernetes, the CVE Numbering Authority that assigned CVE-2020-8561, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).

🔗 References (2)