<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 07:36:45 +0000</lastBuildDate>
    <item>
      <title>GHSA-fcrp-7gc2-93g7 — Envoy Gateway custom backendRef cross-namespace ReferenceGrant bypass</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-fcrp-7gc2-93g7</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/envoyproxy/gateway&lt;/p&gt;
&lt;p&gt;### 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.&lt;/p&gt;
&lt;p&gt;### 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)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/envoyproxy/gateway&lt;/p&gt;
&lt;p&gt;### 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.&lt;/p&gt;
&lt;p&gt;### 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)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-fcrp-7gc2-93g7</guid>
    </item>
  </channel>
</rss>
