How severe is CVE-2023-3893?

CVE-2023-3893 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2023-3893?

CVE-2023-3893 affects the following packages: github.com/kubernetes-csi/csi-proxy/v2 (Go), github.com/kubernetes-csi/csi-proxy (Go), github.com/kubernetes-csi/csi-proxy (Go), github.com/kubernetes-csi/csi-proxy (Go). Ecosystems affected: Go.

How do I fix CVE-2023-3893?

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 CVE-2023-3893 is resolved across your whole dependency graph.

How do I detect CVE-2023-3893 in my Go dependencies?

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.

How do I mitigate CVE-2023-3893 if there is no patch (or I can't update yet)?

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.

Is CVE-2023-3893 actively exploited in the wild?

No public exploit code has been indexed for CVE-2023-3893 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2023-3893?

CVE-2023-3893 has an EPSS (Exploit Prediction Scoring System) score of 2.5%, placing it in the 85th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2023-3893?

CVE-2023-3893 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2023-3893 published, and has it been updated?

CVE-2023-3893 was published on November 3, 2023 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

HIGH severity

CVE-2023-3893 — csi-proxy

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

CVE-2023-3893 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.

Kubernetes - csi-proxy - Insufficient input sanitization leads to privilege escalation

Also known asGHSA-r6cc-7wj7-gfx2GO-2023-2176

Published

Nov 3, 2023

Updated

Oct 28, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Nov 4, 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

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

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/kubernetes-csi/csi-proxy/v2`	≥ 2.0.0-alpha.0&&< 2.0.0-alpha.1	2.0.0-alpha.1`go get github.com/kubernetes-csi/csi-proxy/v2@v2.0.0-alpha.1`
🐹Go	`github.com/kubernetes-csi/csi-proxy`	≥ 0.1.0-rc1&&< 1.1.3	1.1.3`go get github.com/kubernetes-csi/csi-proxy@v1.1.3`
🐹Go	`github.com/kubernetes-csi/csi-proxy`	all versions	0.0.0-20230821192013-2523e6674ded`go get github.com/kubernetes-csi/csi-proxy@v0.0.0-20230821192013-2523e6674ded`
🐹Go	`github.com/kubernetes-csi/csi-proxy`	≥ 1.1.3-0&&< 1.1.3-0.20230821192013-2523e6674ded	1.1.3-0.20230821192013-2523e6674ded`go 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

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.
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 CVE-2023-3893 is resolved across your whole dependency graph.
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.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2023-3893 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

8.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CWE Classification

CWE-20Improper Input Validation

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Nov 3, 2023

Last updated

Oct 28, 2026

Identifiers

CVE-2023-3893

GHSA-r6cc-7wj7-gfx2

GO-2023-2176

References

Advisorygithub.com · CVE 2023 3893.json Advisorynvd.nist.gov · CVE 2023 3893 Advisorysecurity.netapp.com · ntap 20231221 0004 Reportgithub.com Articlegroups.google.com · lWksE2BoCyQ Webgithub.com · 0e83a68159111e4ee510f5aa56d47ba97bda60c7 Webgithub.com · 2523e6674dedf3de27f84235efec28555da24664 Websecurity.netapp.com · ntap 20231221 0004 Packagegithub.com · csi proxy

Related vulnerabilities

This CVE is high severity; 5 of 8 other CVEs with CWE-20 are rated as high or higher (top: critical).

GHSA-fmc8-p6q7-75ccGHSA-pjff-c2wc-f6jmCVE-2026-44265CVE-2026-119280CVE-2026-96631CVE-2026-119210CVE-2026-59978GHSA-c33x-vcv4-vg3gBrowse all CWE-20

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2023-3893 — csi-proxy

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2023-3893 in your dependencies?