Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5amended

Skipper has OPA body-authz bypass: truncated_body mitigation fails open on chunked/HTTP-2 (incomplete fix GHSA-8qqm-fp2q-v734)

CVE-2026-86043GHSA-5gpm-rgj3-9q76

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/zalando/skipper 0.27.37), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS
  • CVE-2026-86043: 0.45% estimated exploitation activity in the next 30 days; percentile 39.24 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

- Affected component: filters/openpolicyagent/openpolicyagent.go → ExtractHttpBodyOptionally; combined with github.com/open-policy-agent/opa-envoy-plugin envoyauth/request.go → getParsedBody / checkIfHTTPBodyTruncated. Filter: opaAuthorizeRequestWithBody. - Affected versions: <= 0.27.33 (current HEAD e7d7014c). The truncatedbody mitigation was introduced/recommended in v0.27.26 (advisory GHSA-8qqm-fp2q-v734) and remains bypassable. - Fix chain being audited: CVE-2026-50197 (GHSA-659f-rgp5-w4wf, commit 3152f3b0) → GHSA-8qqm-fp2q-v734 (docs + code, commit 1be950cd #4126, v0.27.26). This finding is the third, still-open variant. Summary Skipper's opaAuthorizeRequestWithBody filter authorizes requests by handing the (bounded) request body to Open Policy Agent. When a body exceeds -open-policy-agent-max-request-body-size (default 1 MB), Skipper truncates it before OPA sees it. Advisory GHSA-8qqm-fp2q-v734 established that deny-on-presence / body-inspecting policies fail OPEN on oversized…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-5gpm-rgj3-9q76

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6495

  3. Revision 1 · created ·

    Published from osv record GHSA-5gpm-rgj3-9q76

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-86043

Advisory: Skipper has OPA body-authz bypass: truncated_body mitigation fails open on chunked/HTTP-2 (incomplete fix GHSA-8qqm-fp2q-v734)
IDs: CVE-2026-86043, GHSA-5gpm-rgj3-9q76
Record: https://patchnext.com/advisories/cve-2026-86043 (revision 3, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/zalando/skipper 0.27.37. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/zalando/skipper: affected < 0.27.37; fixed in 0.27.37

## Suggested inspection (read-only)
- Go github.com/zalando/skipper: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/zalando/skipper.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-5gpm-rgj3-9q76 (OSV record GHSA-5gpm-rgj3-9q76 lists affected ranges: Go github.com/zalando/skipper >=0 <0.27.37 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6495 (OSV record GO-2026-6495 lists affected ranges: Go github.com/zalando/skipper >=0 <0.27.37 (fixed))
- Verified: https://github.com/advisories/GHSA-5gpm-rgj3-9q76 (GitHub-reviewed advisory GHSA-5gpm-rgj3-9q76 lists affected ranges: Go github.com/zalando/skipper >=0 <0.27.37)

Commands are suggestions: review each one before running it.

Loading voting…