<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-01T10:06:02.124336+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/fkie_cve-2026-65838</id>
    <title>fkie_cve-2026-65838</title>
    <updated>2026-10-01T10:06:02.126992+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2026-65838"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-8qqm-fp2q-v734</id>
    <title>GHSA-8qqm-fp2q-v734 — Skipper: Incomplete fix for CVE-2026-50197: an oversized body can bypass OPA deny-on-presence Rego policies</title>
    <updated>2026-10-01T10:06:02.127270+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/zalando/skipper</p>
<p>### Summary</p>
<p>A wrong policy can be an open door. 
You have to check `input.attributes.request.http.truncated_body` in your policy.</p>
<p>### Description</p>
<p>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.</p>
<p>The CVE-2026-50197 fix (commit `3152f3b0`, PR #4041, v0.26.10) substituted `expectedSize = maxBodyBytes`
only when `req.ContentLength &lt; 0` (chunked / HTTP/2 without content-length). But when a request declares a
`Content-Length` larger than `maxBodyBytes`, `expectedSize &gt; 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.&lt;forbidden&gt;`) — 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.</p>
<p>### Affected code</p>
<p>- `filters/openpolicyagent/openpolicyagent.go` `ExtractHttpBodyOptionally`: the
  `expectedSize &lt;= maxBodyBytes` gate lets an oversized declared body fall through to
  `return req.Body, nil, func() {}, nil` (OPA sees an empty document).
- Corroborated by Skipper's own unit test "Read body exhausting max bytes…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-8qqm-fp2q-v734"/>
  </entry>
</feed>
