Allocation of Resources Without Limits or Throttling Affecting github.com/zalando/skipper/dataclients/kubernetes/admission package, versions <0.26.22
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Allocation of Resources Without Limits or Throttling vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-GOLANG-GITHUBCOMZALANDOSKIPPERDATACLIENTSKUBERNETESADMISSION-19883928
- published17 Sept 2026
- disclosed14 Sept 2026
- creditalcls01111
Introduced: 14 Sep 2026
NewCVE-2026-54247 Â (opens in a new tab)How to fix?
Upgrade github.com/zalando/skipper/dataclients/kubernetes/admission to version 0.26.22 or higher.
Overview
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling due to unbounded request body reads in the Kubernetes admission webhook handler in dataclients/kubernetes/admission/admission.go. An attacker can exhaust memory and OOM-kill the skipper process by sending a very large POST request body to the admission webhook endpoint. The handler reads the entire attacker-controlled body with io.ReadAll(r.Body) before parsing the admission review, so a client with network access to the webhook can force the process to allocate excessive memory. When the process is killed, Kubernetes admission control for the affected resources is disrupted until Skipper restarts.