<?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-06T07:36:46.046088+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/ghsa-fcrp-7gc2-93g7</id>
    <title>GHSA-fcrp-7gc2-93g7 — Envoy Gateway custom backendRef cross-namespace ReferenceGrant bypass</title>
    <updated>2026-10-06T07:36:46.047191+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/envoyproxy/gateway</p>
<p>### Impact
Envoy Gateway accepts extension-managed custom backendRefs from an HTTPRoute to a backend resource in another namespace without requiring a matching Gateway API ReferenceGrant in the target namespace. This breaks the Gateway API cross-namespace consent model: the namespace that owns the referenced backend resource does not need to opt in with a ReferenceGrant before another namespace’s HTTPRoute can use that resource.</p>
<p>### Patches
[1.7.4](https://github.com/envoyproxy/gateway/releases/tag/v1.7.4)
[1.8.1](https://github.com/envoyproxy/gateway/releases/tag/v1.8.1)</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-fcrp-7gc2-93g7"/>
  </entry>
</feed>
