cve.bz

CVE-2026-65838 zalando skipper

8.2 highEPSS 0.5%Fix available

High (8.2) in zalando skipper. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/zalando/skipper 0.27.26.

On this page
Skipper is an HTTP router and reverse proxy for service composition. Prior to 0.27.35, the opaAuthorizeRequestWithBody filter in filters/openpolicyagent/openpolicyagent.go can allow an oversized declared Content-Length request to bypass a deny-on-presence Rego policy because ExtractHttpBodyOptionally leaves OPA with an empty parsed_body while forwarding the complete request body upstream. This incomplete remediation of CVE-2026-50197 affects deployments that authorize request-body content and exceed -open-policy-agent-max-request-body-size, which defaults to 1 MB. Policy logic that does not reject input.attributes.request.http.truncated_body can therefore fail open and permit a forbidden payload to reach the protected service, while small bodies and the previously fixed chunked-body case are evaluated normally. This issue is fixed in version 0.27.35.

Severity

CVSS 3.1

8.2 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 41st percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-09-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-754 Improper Check for Unusual or Exceptional Conditions
OWASP Top 10
A10:2025 Mishandling of Exceptional Conditions
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • github.com/zalando/skipper (Go): fixed in 0.27.26

Ask an AI about this CVE

Show the promptExplain CVE-2026-65838 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-65838?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-65838?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-65838 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
zalando skipper< 0.27.35

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-8qqm-fp2q-v734Gogithub.com/zalando/skipper<0.27.260.27.26
GO-2026-6019Gogithub.com/zalando/skipper<0.27.260.27.26

References

Check your stackJSON