<?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-05T21:16:38.867157+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-168845</id>
    <title>EUVD-2026-168845</title>
    <updated>2026-10-05T21:16:38.915652+00:00</updated>
    <content>EUVD-2026-168845</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-168845"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2019-3779</id>
    <title>fkie_cve-2019-3779</title>
    <updated>2026-10-05T21:16:38.915744+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Cloud Foundry Container Runtime, versions prior to 0.29.0, deploys Kubernetes clusters utilize the same CA (Certificate Authority) to sign and trust certs for ETCD as used by the Kubernetes API. This could allow a user authenticated with a cluster to request a signed certificate leveraging the Kubernetes CSR capability to obtain a credential that could escalate privilege access to ETCD.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2019-3779"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-pw4q-58pr-v79g</id>
    <title>GHSA-pw4q-58pr-v79g</title>
    <updated>2026-10-05T21:16:38.915803+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Cloud Foundry Container Runtime, versions prior to 0.29.0, deploys Kubernetes clusters utilize the same CA (Certificate Authority) to sign and trust certs for ETCD as used by the Kubernetes API. This could allow a user authenticated with a cluster to request a signed certificate leveraging the Kubernetes CSR capability to obtain a credential that could escalate privilege access to ETCD.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-pw4q-58pr-v79g"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2019-3779</id>
    <title>gsd-2019-3779</title>
    <updated>2026-10-05T21:16:38.915841+00:00</updated>
    <content>gsd-2019-3779</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2019-3779"/>
  </entry>
</feed>
