GHSA-fp37-c92q-4pwq is a high-severity (CVSS 8.1) Improper Input Validation vulnerability in k8s.io/apiextensions-apiserver. O3 Security confirms whether GHSA-fp37-c92q-4pwq is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Kubernetes kube-apiserver unauthorized access
Real-World Exposure
k8s.io/apiextensions-apiserver🐹k8s.io/apiextensions-apiserver🐹k8s.io/apiextensions-apiserverReal-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
The Kubernetes kube-apiserver mistakenly allows access to a cluster-scoped custom resource if the request is made as if the resource were namespaced. Authorizations for the resource accessed in this manner are enforced using roles and role bindings within the namespace, meaning that a user with access only to a resource in one namespace could create, view update or delete the cluster-scoped resource (according to their namespace role privileges). Kubernetes affected versions include versions prior to 1.13.9, versions prior to 1.14.5, versions prior to 1.15.2, and versions 1.7, 1.8, 1.9, 1.10, 1.11, 1.12.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | k8s.io/apiextensions-apiserver | ≥ 0.7.0&&< 0.13.9 | 0.13.9 |
| 🐹Go | k8s.io/apiextensions-apiserver | ≥ 0.14.0&&< 0.14.5 | 0.14.5 |
| 🐹Go | k8s.io/apiextensions-apiserver | ≥ 0.15.0&&< 0.15.2 | 0.15.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for k8s.io/apiextensions-apiserver. 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.
Fix
Update k8s.io/apiextensions-apiserver to 0.13.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fp37-c92q-4pwq 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.
How O3 protects you
O3 pinpoints whether GHSA-fp37-c92q-4pwq 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-fp37-c92q-4pwq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-fp37-c92q-4pwq in your dependencies?
O3 detects GHSA-fp37-c92q-4pwq across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.