Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

CVE-2023-5528 kubernetes

HIGHFix: kubernetes/kubernetes#121881

CVE-2023-5528 is a high-severity (CVSS 7.2) Improper Input Validation vulnerability in k8s.io/kubernetes. A fix is available for k8s.io/kubernetes — see the affected versions and patch details below.

Kubernetes - Windows nodes - Insufficient input sanitization in in-tree storage plugin leads to privilege escalation

Also known asGHSA-hq6q-c2x6-hmchGO-2023-2341
Published
Nov 14, 2023
Updated
Aug 12, 2026
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Sep 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
4.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs91th percentile — riskier than 91% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

CVE-2023-5528 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

4 pkgs affected
🐹k8s.io/kubernetes🐹k8s.io/kubernetes🐹k8s.io/kubernetes🐹k8s.io/kubernetes

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
🐹Gok8s.io/kubernetes1.28.0&&< 1.28.41.28.4go get k8s.io/kubernetes@v1.28.4
🐹Gok8s.io/kubernetes1.27.0&&< 1.27.81.27.8go get k8s.io/kubernetes@v1.27.8
🐹Gok8s.io/kubernetes1.26.0&&< 1.26.111.26.11go get k8s.io/kubernetes@v1.26.11
🐹Gok8s.io/kubernetesall versions1.25.16go get k8s.io/kubernetes@v1.25.16

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for k8s.io/kubernetes, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update k8s.io/kubernetes to 1.28.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-5528 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2023-5528 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2023-5528. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Any Kubernetes environment with Windows nodes is impacted. Run kubectl get nodes -l kubernetes.io/os=windows to see if any Windows nodes are in use. Kubernetes audit logs can be used to detect if this vulnerability is being exploited. Persistent Volume create events with local path fields containing special…

ProductFixed inAdvisory
Red Hat OpenShift Container Platform 4.11openshift4-wincw/windows-machine-config-operator-bundle:v6.0.3-8RHSA-2023:7662
Red Hat OpenShift Container Platform 4.12openshift4-wincw/windows-machine-config-operator-bundle:v7.2.0-29RHSA-2023:7710
Red Hat OpenShift Container Platform 4.13openshift4-wincw/windows-machine-config-operator-bundle:v8.1.1-7RHSA-2023:7709
Red Hat OpenShift Container Platform 4.14openshift4-wincw/windows-machine-config-operator-bundle:v9.0.1-15RHSA-2024:1203
Red Hat OpenShift Container Platform 4.15openshift4-wincw/windows-machine-config-operator-bundle:v10.15.0-43RHSA-2024:0954

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2023-5528 in your dependencies?

O3 Security finds CVE-2023-5528 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

CVE-2023-5528: kubernetes (High 7.2) | O3 Security