# CVE-2026-50197: Skipper: opaAuthorizeRequestWithBody filter bypasses OPA policy on Transfer-Encoding: chunked / HTTP/2 requests

> Attackers can bypass Open Policy Agent body inspection in Skipper by using chunked or HTTP/2 requests, allowing unauthorized payloads to reach upstream services.

- **Severity:** High 7.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Jul 2026
- **Updated:** 20 Jul 2026
- **Also known as:** GHSA-659f-rgp5-w4wf, GO-2026-5944

## What is CVE-2026-50197?

CVE-2026-50197 is a high-severity vulnerability in zalando skipper, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Skipper is an HTTP router and reverse proxy for service composition. Prior to 0.26.10, zalando/skipper's OpenPolicyAgent integration silently bypasses request-body inspection on HTTP/1.1 Transfer-Encoding: chunked and HTTP/2 requests that omit the content-length pseudo-header, because the opaAuthorizeRequestWithBody filter and OpenPolicyAgentInstance.ExtractHttpBodyOptionally in filters/openpolicyagent/openpolicyagent.go produce an empty raw_body and input.parsed_body while the upstream service receives the full attacker-controlled body. This issue is fixed in version 0.26.10.

Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests)

## Which versions are affected by CVE-2026-50197?

3 open source packages ship an affected version, including github.com/zalando/skipper.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/zalando/skipper` | Go | All versions | 0.26.10 |
| `github.com/zalando/skipper` | Go | All versions | 0.26.10 |
| `github.com/zalando/skipper` | Go | All versions | 0.26.10 |

## How do I fix CVE-2026-50197?

Upgrade github.com/zalando/skipper to 0.26.10 or later.

## Is CVE-2026-50197 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-50197 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-50197 and fix it if it is affected.

What it is: CVE-2026-50197 is a high-severity vulnerability in zalando skipper, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-50197 exists.

Affected packages and fixed versions:
- github.com/zalando/skipper (Go): affected all versions; fixed in 0.26.10
- github.com/zalando/skipper (Go): affected all versions; fixed in 0.26.10
- github.com/zalando/skipper (Go): affected all versions; fixed in 0.26.10

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-50197/ (Markdown: https://insights.sbomify.com/CVE-2026-50197/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-50197
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-50197
- OSV: https://osv.dev/vulnerability/CVE-2026-50197

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-50197/
Summaries are generated and may contain mistakes; the official description above is the record.