CVE-2026-65838: Skipper: Incomplete fix for CVE-2026-50197: an oversized body can bypass OPA deny-on-presence Rego policies
Summary A wrong policy can be an open door. You have to check input.attributes.request.http.truncatedbody in your policy. Description Incomplete fix for CVE-2026-50197: an oversized declared-Content-Length body still hands OPA an empty parsedbody, so deny-on-presence Rego policies fail OPEN while the full payload reaches upstream.
Published Jul 17, 2026 · Updated Sep 25, 2026
Affected packages
github.com/zalando/skipper
- Ecosystem
- Go
- Affected
- < 0.27.26
- Fixed in
- 0.27.26
- Check
go list -m github.com/zalando/skipper
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
A wrong policy can be an open door. You have to check input.attributes.request.http.truncated_body in your policy.
Description
Incomplete fix for CVE-2026-50197: an oversized declared-Content-Length body still hands OPA an empty parsed_body, so deny-on-presence Rego policies fail OPEN while the full payload reaches upstream.
The CVE-2026-50197 fix (commit 3152f3b0, PR #4041, v0.26.10) substituted expectedSize = maxBodyBytes only when req.ContentLength < 0 (chunked / HTTP/2 without content-length). But when a request declares a Content-Length larger than maxBodyBytes, expectedSize > maxBodyBytes, the body-extraction if is skipped entirely, and ExtractHttpBodyOptionally returns rawBodyBytes = nil — so OPA evaluates an empty parsed_body, while the full forbidden payload still flows to the upstream. A deny-on-presence policy (default allow = true; allow = false if input.parsed_body.<forbidden>) — the exact Rego shape the advisory describes — fails OPEN. The fix's own comment reasons only about ContentLength == -1; the oversized branch was never considered, and the added PoC test only covers small bodies.
Affected code
filters/openpolicyagent/openpolicyagent.goExtractHttpBodyOptionally: theexpectedSize <= maxBodyBytesgate lets an oversized declared body fall through toreturn req.Body, nil, func() {}, nil(OPA sees an empty document).- Corroborated by Skipper's own unit test "Read body exhausting max bytes" (
{ "welcome": "world" },maxBodySize: 5→bodyInPolicy: "").
Steps to reproduce
See attached docker-compose.yml (official golang image) + setup.sh + exploit.sh, which run a real Skipper proxy (proxytest) with a real OPA control plane (opasdktest), WithMaxRequestBodyBytes(32), policy allow = false if input.parsed_body.action == "delete", route * -> opaAuthorizeRequestWithBody("test") -> upstream:
{"action":"delete"}(19B ≤ 32) → 403 (denied).{"action":"delete","pad":"X..64"}(> 32) → 200, upstream received the full body (BYPASS).- small chunked
{"action":"delete"}→ 403 (positive control: the original CVE is fixed).
(Library-tier: validated via Skipper's real proxy test harness, not a deploy of the official image; benign oracle = status diff + upstream-received body; no RCE.)
Impact
Deployments authorizing on request-body content via opaAuthorizeRequestWithBody + deny-on-presence Rego can be bypassed by inflating the request body past -open-policy-agent-max-request-body-size (default 1 MB); the full payload still reaches the upstream.
Mitigation
Document how policy owners should block requests with oversized body.
Example deny by default and use "allow if" no oversized body:
default allow := false
allow if {
input.attributes.request.http.truncated_body == false
# ... body-based conditions
}Example allow by default and use "deny if" an oversized body:
default deny := false
deny if {
input.attributes.request.http.truncated_body == true
# ... body-based conditions
}Documentation is published by https://github.com/zalando/skipper/releases/tag/v0.27.26
Credit
Reported as part of an incomplete-patch measurement study (responsible disclosure).
Credited to sec-reex, deepakravisankar.
References
- https://github.com/zalando/skipper/security/advisories/GHSA-8qqm-fp2q-v734
- https://github.com/zalando/skipper/releases/tag/v0.27.26
- https://nvd.nist.gov/vuln/detail/CVE-2026-65838
- https://github.com/zalando/skipper/commit/2cfceabaa6ff0af65b312dcb9bcbe84691b9d507
- https://github.com/zalando/skipper/releases/tag/v0.27.35
- https://github.com/advisories/GHSA-8qqm-fp2q-v734
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-86043
Skipper has OPA body-authz bypass: truncated_body mitigation fails open on chunked/HTTP-2 (incomplete fix GHSA-8qqm-fp2q-v734)
high7.5Sep 17, 2026CVE-2026-54246
Skipper's routesrv-no-auth component: All routesrv API Endpoints Lack Authentication
medium5.7Jul 17, 2026CVE-2026-54247
Skipper: Unbounded Request Body Read in Admission Webhook Causes Memory Exhaustion DoS
medium4.3Jul 17, 2026CVE-2026-50197
Skipper: opaAuthorizeRequestWithBody filter bypasses OPA policy on Transfer-Encoding — chunked / HTTP/2 requests
high8.7Jul 8, 2026CVE-2026-24470
Skipper Ingress Controller Allows Unauthorized Access to Internal Services via ExternalName
high8.1Jan 26, 2026CVE-2026-23742
Skipper is vulnerable to arbitrary code execution through lua filters
high8.8Jan 16, 2026
