<?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://cve.radiocsirt.org</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 16:03:56 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-368643</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-368643</link>
      <description>EUVD-2026-368643</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-368643</guid>
    </item>
    <item>
      <title>fkie_cve-2026-16141</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-16141</link>
      <description>&lt;p&gt;OpenBMC&amp;#39;s IPMI implementation, phosphor-net-ipmid, contains a logic flaw in which an unauthenticated client can force the RAKP Message 1 handler to return before it overwrites the authentication object&amp;#39;s constructor defaults. The IPMI service then accepts a RAKP Message 3 whose HMAC is computed with the constant 20-byte &amp;#39;userKey&amp;#39; initialized from the string &amp;#39;0penBmc&amp;#39; and an often-predictable &amp;#39;bmcRandomNum&amp;#39;. Several downstream vendors implement phosphor-net-ipmid as their IPMI stack, such as NVIDIA and H3C.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;OpenBMC&amp;#39;s IPMI implementation, phosphor-net-ipmid, contains a logic flaw in which an unauthenticated client can force the RAKP Message 1 handler to return before it overwrites the authentication object&amp;#39;s constructor defaults. The IPMI service then accepts a RAKP Message 3 whose HMAC is computed with the constant 20-byte &amp;#39;userKey&amp;#39; initialized from the string &amp;#39;0penBmc&amp;#39; and an often-predictable &amp;#39;bmcRandomNum&amp;#39;. Several downstream vendors implement phosphor-net-ipmid as their IPMI stack, such as NVIDIA and H3C.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-16141</guid>
    </item>
    <item>
      <title>GHSA-28w7-pg33-g2hj</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-28w7-pg33-g2hj</link>
      <description>&lt;p&gt;OpenBMC&amp;#39;s IPMI implementation, phosphor-net-ipmid, contains a logic flaw in which an unauthenticated client can force the RAKP Message 1 handler to return before it overwrites the authentication object&amp;#39;s constructor defaults. The IPMI service then accepts a RAKP Message 3 whose HMAC is computed with the constant 20-byte &amp;#39;userKey&amp;#39; initialized from the string &amp;#39;0penBmc&amp;#39; and an often-predictable &amp;#39;bmcRandomNum&amp;#39;. Several downstream vendors implement phosphor-net-ipmid as their IPMI stack, such as NVIDIA and H3C.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;OpenBMC&amp;#39;s IPMI implementation, phosphor-net-ipmid, contains a logic flaw in which an unauthenticated client can force the RAKP Message 1 handler to return before it overwrites the authentication object&amp;#39;s constructor defaults. The IPMI service then accepts a RAKP Message 3 whose HMAC is computed with the constant 20-byte &amp;#39;userKey&amp;#39; initialized from the string &amp;#39;0penBmc&amp;#39; and an often-predictable &amp;#39;bmcRandomNum&amp;#39;. Several downstream vendors implement phosphor-net-ipmid as their IPMI stack, such as NVIDIA and H3C.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-28w7-pg33-g2hj</guid>
    </item>
  </channel>
</rss>
