<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-25T06:44:27.568248+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/euvd-2026-260380</id>
    <title>EUVD-2026-260380</title>
    <updated>2026-10-25T06:44:27.570372+00:00</updated>
    <content>EUVD-2026-260380</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-260380"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2025-64323</id>
    <title>fkie_cve-2025-64323</title>
    <updated>2026-10-25T06:44:27.570403+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>kgateway is a Cloud-Native API and AI Gateway. Versions 2.0.4 and below and 2.1.0-agw-cel-rbac through 2.1.0-rc.2 lack authentication, allowing any client with unrestricted network access to the xDS port to retrieve potentially sensitive configuration data including certificate data, backend service information, routing rules, and cluster metadata. This issue is solved in versions 2.0.5 and 2.1.0.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2025-64323"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-4766-x535-jw3r</id>
    <title>GHSA-4766-x535-jw3r — kgateway is missing xDS authorization</title>
    <updated>2026-10-25T06:44:27.570434+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/kgateway-dev/kgateway/v2</p>
<p>## Summary</p>
<p>The xDS interface in Kgateway versions 2.0.0 through 2.0.4 lacks authentication, allowing any client with unrestricted network access to the xDS port to retrieve potentially sensitive configuration data including certificate data, backend service information, routing rules, and cluster metadata.</p>
<p>## Description</p>
<p>### Impact</p>
<p>Kgateway xDS interface did not have authorization, so anonymous clients with unrestricted network access could gain access to the xDS data. This could expose sensitive information about your gateway configuration, certificate data, backend services, and routing topology to unauthorized parties.</p>
<p>### Patches</p>
<p>Upgrade to version 2.0.5 or 2.1.0. These versions enable JWT-based authentication for the xDS interface by default, ensuring that only authenticated clients can access the xDS configuration data.</p>
<p>### Workarounds</p>
<p>If immediate upgrade is not possible, NetworkPolicies can be used to block access to kgateway's xDS port, restricting network access to only trusted sources.</p>
<p>## References</p>
<p>- Fix in 2.1.0: https://github.com/kgateway-dev/kgateway/pull/12471
- Backport to 2.0.5: https://github.com/kgateway-dev/kgateway/pull/12535
- Related issue: https://github.com/kgateway-dev/kgateway/issues/10651</p>
<p>## Credits</p>
<p>Kindly reported by @rikatz</p>
<p>## For More Information</p>
<p>If you have any questions or comments about this advisory, please reach out in slack https://cloud-native.slack.com/archives/C080D3PJMS4</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-4766-x535-jw3r"/>
  </entry>
</feed>
