NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

Kubernetes csi-proxy vulnerable to privilege escalation due to improper input validationGHSA-r6cc-7wj7-gfx2

HIGHFix: kubernetes-csi/csi-proxy@0e83a68

GHSA-r6cc-7wj7-gfx2 is a high-severity (CVSS 8.8) Improper Input Validation vulnerability in github.com/kubernetes-csi/csi-proxy/v2. A fix is available for github.com/kubernetes-csi/csi-proxy/v2 — see the affected versions and patch details below.

Also known asCVE-2023-3893GO-2023-2176
Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs85th percentile — riskier than 85% of all scored CVEsHighest risk
1.98%2.71%3.45%4.19%3.7%2.5%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected
🐹github.com/kubernetes-csi/csi-proxy/v2🐹github.com/kubernetes-csi/csi-proxy🐹github.com/kubernetes-csi/csi-proxy🐹github.com/kubernetes-csi/csi-proxy

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 on Windows nodes running kubernetes-csi-proxy may be able to escalate to admin privileges on those nodes. Kubernetes clusters are only affected if they include Windows nodes running kubernetes-csi-proxy.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/kubernetes-csi/csi-proxy/v2≥ 2.0.0-alpha.0&&< 2.0.0-alpha.12.0.0-alpha.1go get github.com/kubernetes-csi/csi-proxy/v2@v2.0.0-alpha.1
🐹Gogithub.com/kubernetes-csi/csi-proxy≥ 0.1.0-rc1&&< 1.1.31.1.3go get github.com/kubernetes-csi/csi-proxy@v1.1.3
🐹Gogithub.com/kubernetes-csi/csi-proxyall versions0.0.0-20230821192013-2523e6674dedgo get github.com/kubernetes-csi/csi-proxy@v0.0.0-20230821192013-2523e6674ded
🐹Gogithub.com/kubernetes-csi/csi-proxy≥ 1.1.3-0&&< 1.1.3-0.20230821192013-2523e6674ded1.1.3-0.20230821192013-2523e6674dedgo get github.com/kubernetes-csi/csi-proxy@v1.1.3-0.20230821192013-2523e6674ded

Affected Products

1 product · 2 configurations
Application
csi proxykubernetes
≤ 1.1.2
1 version
2.0.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update github.com/kubernetes-csi/csi-proxy/v2 to 2.0.0-alpha.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r6cc-7wj7-gfx2 is resolved across your whole dependency graph.

  3. Workarounds

    Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Frequently Asked Questions

Kubernetes is vulnerable to privilege escalation when a user that can create pods on Windows nodes running kubernetes-csi-proxy may be able to escalate to admin privileges on those nodes. Kubernetes clusters are only affected if they include Windows nodes running kubernetes-csi-proxy.
O3 Security · Impact-Aware SCA

Is GHSA-r6cc-7wj7-gfx2 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
Kubernetes csi-proxy vulnerable to privilege escalation…