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

NULL Pointer Dereference in Kubernetes CSI snapshot-controllerGHSA-hwrr-rhmm-vcvf

MEDIUM

GHSA-hwrr-rhmm-vcvf is a medium-severity (CVSS 6.5) NULL Pointer Dereference vulnerability in github.com/kubernetes-csi/external-snapshotter/v2. 1 public exploit reference exists, so weaponization risk is real. A fix is available for github.com/kubernetes-csi/external-snapshotter/v2 — see the affected versions and patch details below.

Also known asCVE-2020-8569
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
1 known
Exploitation data as of Oct 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs83th percentile — riskier than 83% of all scored CVEsHighest risk
0.00%0.95%1.90%2.85%0.3%2.3%Apr 26Aug 26Oct 26

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

How urgent is this, really

GHSA-hwrr-rhmm-vcvf by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected
🐹github.com/kubernetes-csi/external-snapshotter/v2🐹github.com/kubernetes-csi/external-snapshotter/v3

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

Kubernetes CSI snapshot-controller prior to v2.1.3 and v3.0.2 could panic when processing a VolumeSnapshot custom resource when:

  • The VolumeSnapshot referenced a non-existing PersistentVolumeClaim and the VolumeSnapshot did not reference any VolumeSnapshotClass.
  • The snapshot-controller crashes, is automatically restarted by Kubernetes, and processes the same VolumeSnapshot custom resource after the restart, entering an endless crashloop.

Only the volume snapshot feature is affected by this vulnerability. When exploited, users can’t take snapshots of their volumes or delete the snapshots. All other Kubernetes functionality is not affected.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/kubernetes-csi/external-snapshotter/v2≥ 2.0.0&&< 2.1.32.1.3go get github.com/kubernetes-csi/external-snapshotter/v2@v2.1.3
🐹Gogithub.com/kubernetes-csi/external-snapshotter/v3≥ 3.0.0&&< 3.0.23.0.2go get github.com/kubernetes-csi/external-snapshotter/v3@v3.0.2

Affected Products

1 product · 2 configurations
Application
container storage interface snapshotterkubernetes
≥ 3.0.0 && < 3.0.2
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

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/external-snapshotter/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/kubernetes-csi/external-snapshotter/v2 to 2.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hwrr-rhmm-vcvf 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.

Frequently Asked Questions

Kubernetes CSI snapshot-controller prior to v2.1.3 and v3.0.2 could panic when processing a VolumeSnapshot custom resource when: - The VolumeSnapshot referenced a non-existing PersistentVolumeClaim and the VolumeSnapshot did not reference any VolumeSnapshotClass. - The snapshot-controller crashes, is automatically restarted by Kubernetes, and processes the same VolumeSnapshot custom resource after the restart, entering an endless crashloop. Only the volume snapshot feature is affected by this vulnerability. When exploited, users can’t take snapshots of their volumes or delete the snapshots
O3 Security · Impact-Aware SCA

Is GHSA-hwrr-rhmm-vcvf in your dependencies?

Find it across Go, including transitive dependencies.

NULL Pointer Dereference in Kubernetes CSI…