Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

GHSA-q4rr-64r9-fwgf

MEDIUM

Kubernetes DoS Vulnerability

Also known asCVE-2019-1002100GO-2023-1946
Published
May 13, 2022
Updated
Feb 4, 2026
Affected
4 pkgs
Patched
3 / 4
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
10.5%probability of exploitation in next 30 days
Moderate Risk95th percentile+7.84%
0.14%4.65%9.15%13.6%11.1%10.5%Dec 25Apr 26Jun 26

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.

Blast Radius

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

In all Kubernetes versions prior to v1.11.8, v1.12.6, and v1.13.4, users that are authorized to make patch requests to the Kubernetes API Server can send a specially crafted patch of type "json-patch" (e.g. kubectl patch --type json or "Content-Type: application/json-patch+json") that consumes excessive resources while processing, causing a Denial of Service on the API Server.

Affected Packages

4 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐹Gok8s.io/kubernetes1.0.0No fix
🐹Gok8s.io/kubernetes1.11.0&&< 1.11.81.11.8
🐹Gok8s.io/kubernetes1.12.0&&< 1.12.61.12.6
🐹Gok8s.io/kubernetes1.13.0&&< 1.13.41.13.4

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    No patched version of k8s.io/kubernetes has shipped for GHSA-q4rr-64r9-fwgf yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  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 pinpoints whether GHSA-q4rr-64r9-fwgf is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-q4rr-64r9-fwgf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In all Kubernetes versions prior to v1.11.8, v1.12.6, and v1.13.4, users that are authorized to make patch requests to the Kubernetes API Server can send a specially crafted patch of type "json-patch" (e.g. `kubectl patch --type json` or `"Content-Type: application/json-patch+json"`) that consumes excessive resources while processing, causing a Denial of Service on the API Server.
O3 Security · Impact-Aware SCA

Is GHSA-q4rr-64r9-fwgf in your dependencies?

O3 detects GHSA-q4rr-64r9-fwgf across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.