/

CVE-2026-86043

Severity:

HIGH RISK

(7.5)

Incorrect Authorization (CWE-863) in Skipper OPA Filter

CVE-2026-86043

Deferred

Vulnerability type

Category:

Authorization Bypass

CWE:

CWE-863

Impact:

Authorization bypass and unintended access to protected upstream services

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Skipper's OPA authorization filter may evaluate only a truncated prefix of an oversized request body while treating the body as complete. Under affected HTTP/1.1 chunked or HTTP/2 request conditions, a body-inspecting policy may approve the request before the full body is forwarded to the protected upstream.

Affected context

The issue occurs in Skipper deployments using the opaAuthorizeRequestWithBody filter with body-inspecting Open Policy Agent policies. Risk is present when requests can exceed the configured body inspection limit and the request uses HTTP/1.1 chunked transfer encoding or HTTP/2 without a Content-Length header, allowing the truncation signal to differ from the bytes actually read.

Exploit preconditions

  • Attack surface: HTTP requests processed by Skipper's OPA body-authorization filter
  • Required access: Ability to send requests through the affected Skipper route; separate policy or application authorization may still apply
  • Trigger point: OPA evaluation after Skipper truncates the body presented for inspection
  • Why exploitation is possible: The input.truncated_body signal can be derived from an unavailable or non-reflective Content-Length value rather than the actual body read result, causing a policy to evaluate an incomplete prefix while the full body is forwarded

Why this happens

The underlying bug is an authorization decision based on incomplete request data combined with an inaccurate truncation indicator. When the adapter copies headers without adding a Content-Length that represents the truncated body, policies that permit only input.truncated_body == false may incorrectly treat a truncated inspection input as complete. This maps to CWE-863, Incorrect Authorization, because the authorization decision can be made from insufficiently represented request content.

Potential impact

  • An unauthorized or insufficiently inspected request may reach a protected upstream
  • Application-level authorization controls could be bypassed for oversized requests
  • Malicious request content beyond the inspected prefix could influence downstream processing
  • Backend services could receive payloads that the OPA policy did not fully evaluate
  • Security, auditing, or content-validation assumptions could be weakened

General mitigation guidance

Mitigation generally focuses on ensuring authorization decisions use the complete

security-relevant request content or fail closed when inspection is incomplete.

Common defensive patterns include:

  • Treating any body truncation, unknown length, or incomplete inspection as an authorization failure
  • Rejecting or separately handling oversized requests before policy evaluation
  • Deriving truncation state from the actual bytes read rather than relying only on request headers
  • Avoiding policies that assume absent or inconsistent length metadata means the body is complete
  • Enforcing consistent request-size limits at the proxy and upstream boundaries
  • Applying least privilege to routes and backend identities so an authorization mistake has limited reach
  • Using downstream validation as defense in depth rather than as a substitute for complete proxy authorization

How teams detect issues like this

Detection can combine implementation review, policy analysis, and runtime monitoring.

  • Use static analysis to identify authorization decisions that depend on incomplete,

truncated, or header-derived request bodies.

  • Review code paths where body limits, transfer encoding, HTTP/2 framing, and

Content-Length handling interact.

  • Flag OPA policies that explicitly permit requests when truncation is false

without independently enforcing size or completeness guarantees.

  • Add tests covering oversized bodies sent with chunked HTTP/1.1 and HTTP/2

requests without Content-Length.

  • Monitor discrepancies between bytes inspected by the policy engine and bytes

forwarded upstream.

  • Enforce policy rules requiring complete body inspection for security-sensitive

routes; automated review tools may help identify inconsistent handling.

Sources

SourceLink
github.comgithub.com/zalando/skipper/commit/2cfceabaa6ff0af65b312dcb9bcbe84691b9d507
github.comgithub.com/zalando/skipper/releases/tag/v0.27.35
github.comgithub.com/zalando/skipper/security/advisories/GHSA-5gpm-rgj3-9q76
github.comgithub.com/zalando/skipper/tree/v0.27.35

Frequently asked

questions

It affects Skipper routes that use body-aware OPA authorization and permit

oversized requests whose bodies are truncated during inspection. Requests using

chunked HTTP/1.1 or HTTP/2 without Content-Length are especially relevant.

The attacker needs the ability to send a request through an affected route.

Whether authentication is required depends on the route and surrounding

access controls; the flaw concerns how an otherwise processed request is

authorized.

Authorization should fail closed whenever the body is incomplete or its

completeness cannot be reliably established. Request-size enforcement and

truncation detection should be based on the actual read result, not only on

Content-Length.

Test authorization logic across HTTP versions and transfer modes, treat

metadata inconsistencies as security-relevant, require complete inspection

for sensitive routes, and keep proxy and upstream request limits aligned.

Find out what's already
exploitable in your codebase.