<?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-09T16:06:11.515754+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-384180</id>
    <title>EUVD-2026-384180</title>
    <updated>2026-10-09T16:06:11.533620+00:00</updated>
    <content>EUVD-2026-384180</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-384180"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-78243</id>
    <title>fkie_cve-2026-78243</title>
    <updated>2026-10-09T16:06:11.533659+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>Apache YuniKorn 1.8.0 and later, if configured with the LDAP group resolver, crashes due to an out of bounds read processing group membership entries.If the LDAP server returns a group membership entry, memberOf attribute, for a user specified in the pod the server crashes if a membership record does not start with "CN=".</p>
<p>This only affects install that have the non default LDAP group provider configured.</p>
<p>Users are recommended to upgrade to version 1.10.0, which fixes this issue.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-78243"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-79rm-9vfm-ggww</id>
    <title>GHSA-79rm-9vfm-ggww</title>
    <updated>2026-10-09T16:06:11.533699+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>Apache YuniKorn 1.8.0 and later, if configured with the LDAP group resolver, crashes due to an out of bounds read processing group membership entries.If the LDAP server returns a group membership entry, memberOf attribute, for a user specified in the pod the server crashes if a membership record does not start with "CN=".</p>
<p>This only affects install that have the non default LDAP group provider configured.</p>
<p>Users are recommended to upgrade to version 1.10.0, which fixes this issue.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-79rm-9vfm-ggww"/>
  </entry>
</feed>
