<?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-19T13:22:02.853461+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/bit-cilium-2024-42486</id>
    <title>BIT-cilium-2024-42486 — Cilium vulnerable to information leakage via incorrect ReferenceGrant update logic in Gateway API</title>
    <updated>2026-10-19T13:22:02.858528+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: cilium</p>
<p>Cilium is a networking, observability, and security solution with an eBPF-based dataplane. In versions on the 1.15.x branch prior to 1.15.8 and the 1.16.x branch prior to 1.16.1, ReferenceGrant changes are not correctly propagated in Cilium's GatewayAPI controller, which could lead to Gateway resources being able to access secrets for longer than intended, or to Routes having the ability to forward traffic to backends in other namespaces for longer than intended. This issue has been patched in Cilium v1.15.8 and v1.16.1. As a workaround, any modification of a related Gateway/HTTPRoute/GRPCRoute/TCPRoute CRD (for example, adding any label to any of these resources) will trigger a reconciliation of ReferenceGrants on an affected cluster.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bit-cilium-2024-42486"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-158858</id>
    <title>EUVD-2026-158858</title>
    <updated>2026-10-19T13:22:02.858598+00:00</updated>
    <content>EUVD-2026-158858</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-158858"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2024-42486</id>
    <title>fkie_cve-2024-42486</title>
    <updated>2026-10-19T13:22:02.858621+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Cilium is a networking, observability, and security solution with an eBPF-based dataplane. In versions on the 1.15.x branch prior to 1.15.8 and the 1.16.x branch prior to 1.16.1, ReferenceGrant changes are not correctly propagated in Cilium's GatewayAPI controller, which could lead to Gateway resources being able to access secrets for longer than intended, or to Routes having the ability to forward traffic to backends in other namespaces for longer than intended. This issue has been patched in Cilium v1.15.8 and v1.16.1. As a workaround, any modification of a related Gateway/HTTPRoute/GRPCRoute/TCPRoute CRD (for example, adding any label to any of these resources) will trigger a reconciliation of ReferenceGrants on an affected cluster.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2024-42486"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-vwf8-q6fw-4wcm</id>
    <title>GHSA-vwf8-q6fw-4wcm — Cilium leaks information via incorrect ReferenceGrant update logic in Gateway API</title>
    <updated>2026-10-19T13:22:02.858660+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/cilium/cilium</p>
<p>### Impact</p>
<p>Due to ReferenceGrant changes not being immediately propagated in Cilium's GatewayAPI controller, Gateway resources are able to access secrets in other namespaces after the associated ReferenceGrant has been revoked. This can lead to Gateways continuing to establish sessions using secrets that they should no longer have access to.</p>
<p>### Patches</p>
<p>This issue was resolved in https://github.com/cilium/cilium/pull/34032.</p>
<p>This issue affects:</p>
<p>- Cilium v1.15 between v1.15.0 and v1.15.7 inclusive
- Cilium v1.16.0</p>
<p>This issue has been patched in:</p>
<p>- Cilium v1.15.8
- Cilium v1.16.1</p>
<p>### Workarounds</p>
<p>Any modification of a related Gateway/HTTPRoute/GRPCRoute/TCPRoute CRD (for example, adding any label to any of these resources) will trigger a reconciliation of ReferenceGrants on an affected cluster.</p>
<p>### Acknowledgements</p>
<p>The Cilium community has worked together with members of Cure53 and Isovalent to prepare these mitigations. Special thanks to @sayboras for resolving this issue.</p>
<p>### For more information</p>
<p>If you have any questions or comments about this advisory, please reach out on [Slack](https://docs.cilium.io/en/latest/community/community/#slack).</p>
<p>If you think you have found a vulnerability affecting Cilium, we strongly encourage you to report it to our security mailing list at [security@cilium.io](mailto:security@cilium.io). This is a private mailing list for the Cilium security team, and your report will be treated as top priority.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-vwf8-q6fw-4wcm"/>
  </entry>
</feed>
