GHSA-2pf9-vr92-6h3v
MEDIUMGHSA-2pf9-vr92-6h3v is a medium-severity (CVSS 6.5) CWE-770 vulnerability in k8s.io/ingress-nginx. O3 Security confirms whether GHSA-2pf9-vr92-6h3v is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
ingress-nginx vulnerable to Allocation of Resources Without Limits or Throttling
Real-World Exposure
k8s.io/ingress-nginx🐹k8s.io/ingress-nginxReal-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 ingress-nginx where the validating admission controller feature is subject to a denial of service condition. By sending large requests to the validating admission controller, an attacker can cause memory consumption, which may result in the ingress-nginx controller pod being killed or the node running out of memory.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | k8s.io/ingress-nginx | all versions | 1.13.7 |
| 🐹Go | k8s.io/ingress-nginx | ≥ 1.14.0&&< 1.14.3 | 1.14.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for k8s.io/ingress-nginx. 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/ingress-nginx to 1.13.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2pf9-vr92-6h3v 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-2pf9-vr92-6h3v 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-2pf9-vr92-6h3v. 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-2pf9-vr92-6h3v in your dependencies?
O3 detects GHSA-2pf9-vr92-6h3v across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.