# CVE-2023-5528: Kubernetes - Windows nodes - Insufficient input sanitization in in-tree storage plugin leads to privilege escalation > Attackers with pod creation rights on Windows nodes using in-tree storage plugins can escalate to admin privileges. - **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 14 Nov 2023 - **Updated:** 25 Feb 2026 - **Also known as:** AZL-32005, AZL-34894, CLEANSTART-2026-EF04271, CLEANSTART-2026-JR27860, GHSA-hq6q-c2x6-hmch, GO-2023-2341 ## What is CVE-2023-5528? CVE-2023-5528 is a high-severity vulnerability in Fedoraproject Fedora, published on 14 Nov 2023. An attacker needs administrator access to exploit it, with no action from the victim. ### Official description A security issue was discovered in Kubernetes where a user that can create pods and persistent volumes on Windows nodes may be able to escalate to admin privileges on those nodes. Kubernetes clusters are only affected if they are using an in-tree storage plugin for Windows nodes. Weakness: CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2023-5528? 9 open source packages ship an affected version, including k8s.io/kubernetes. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `k8s.io/kubernetes` | Go | All versions | 1.25.16, 1.26.11, 1.27.8, 1.28.4 | | `k8s.io/kubernetes` | Go | All versions | 1.25.16 | | `k8s.io/kubernetes` | Go | All versions | 1.25.16 | | `k8s.io/kubernetes` | Go | From 1.26.0 | 1.26.11 | | `k8s.io/kubernetes` | Go | From 1.26.0 | 1.26.11 | | `k8s.io/kubernetes` | Go | From 1.27.0 | 1.27.8 | | `k8s.io/kubernetes` | Go | From 1.27.0 | 1.27.8 | | `k8s.io/kubernetes` | Go | From 1.28.0 | 1.28.4 | | `k8s.io/kubernetes` | Go | From 1.28.0 | 1.28.4 | Products: Fedoraproject Fedora, Kubernetes Kubernetes. ## How do I fix CVE-2023-5528? Upgrade k8s.io/kubernetes to a fixed version for your release line: 1.25.16, 1.26.11, 1.27.8 or 1.28.4. ## Is CVE-2023-5528 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-5528 exists. ## Other vulnerabilities in Fedoraproject Fedora - [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild) - [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild) - [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild) - [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild) - [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-5528 and fix it if it is affected. What it is: CVE-2023-5528 is a high-severity vulnerability in Fedoraproject Fedora, published on 14 Nov 2023. An attacker needs administrator access to exploit it, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-5528 exists. Affected packages and fixed versions: - k8s.io/kubernetes (Go): affected all versions; fixed in 1.25.16, 1.26.11, 1.27.8, 1.28.4 - k8s.io/kubernetes (Go): affected all versions; fixed in 1.25.16 - k8s.io/kubernetes (Go): affected all versions; fixed in 1.25.16 - k8s.io/kubernetes (Go): affected from 1.26.0; fixed in 1.26.11 - k8s.io/kubernetes (Go): affected from 1.26.0; fixed in 1.26.11 - k8s.io/kubernetes (Go): affected from 1.27.0; fixed in 1.27.8 - k8s.io/kubernetes (Go): affected from 1.27.0; fixed in 1.27.8 - k8s.io/kubernetes (Go): affected from 1.28.0; fixed in 1.28.4 - k8s.io/kubernetes (Go): affected from 1.28.0; fixed in 1.28.4 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-2023-5528/ (Markdown: https://insights.sbomify.com/CVE-2023-5528/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-5528 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-5528 - OSV: https://osv.dev/vulnerability/CVE-2023-5528 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-5528/ Summaries are generated and may contain mistakes; the official description above is the record.