<?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>Fri, 02 Oct 2026 15:36:24 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-14713</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-14713</link>
      <description>bdu:2026-14713</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-14713</guid>
    </item>
    <item>
      <title>EUVD-2026-360124</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-360124</link>
      <description>EUVD-2026-360124</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-360124</guid>
    </item>
    <item>
      <title>fkie_cve-2026-58092</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-58092</link>
      <description>&lt;p&gt;In FreeBSD 15.0, the kernel structure used to represent user credentials changed: previously the primary group ID was stored in the first element of the array containing the list of supplementary group IDs, whereas now the primary group ID is stored in a dedicated field.  This change was largely internal to the kernel and not user-visible.&lt;/p&gt;
&lt;p&gt;One function, group_is_primary(), was not properly updated as a part of this transition.  This function is used by mac_do to determine the primary group ID of the credential after applying a transition rule, used when the rule target does not explicitly specify a group.&lt;/p&gt;
&lt;p&gt;As a result, with certain mac_do rules, it is possible for a credential switch to incorrectly set the primary group ID to the ID stored in the first element of the original credential&amp;#39;s supplementary group array.&lt;/p&gt;
&lt;p&gt;If the list of supplementary groups is empty, this value will be 0, corresponding to the &amp;#34;wheel&amp;#34; group.  For example, a rule such as &amp;#34;uid=1001&amp;gt;uid=1002&amp;#34; can be abused to set the primary group ID to 0 even if the process did not originally belong to group 0.&lt;/p&gt;
&lt;p&gt;Certain mac_do rules can be abused to set a process&amp;#39; group ID to 0.  Note however, that the rule must apply to the caller in order for the bug to be triggered, e.g., given the ruleset &amp;#34;uid=1001&amp;gt;uid=1002&amp;#34;, the user must have user ID 1001 in order to trigger the bug.&lt;/p&gt;
&lt;p&gt;Further, logged-in users will in general have a non-empty supplementary group list, in which case the bug can at worst be used to set the cred…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In FreeBSD 15.0, the kernel structure used to represent user credentials changed: previously the primary group ID was stored in the first element of the array containing the list of supplementary group IDs, whereas now the primary group ID is stored in a dedicated field.  This change was largely internal to the kernel and not user-visible.&lt;/p&gt;
&lt;p&gt;One function, group_is_primary(), was not properly updated as a part of this transition.  This function is used by mac_do to determine the primary group ID of the credential after applying a transition rule, used when the rule target does not explicitly specify a group.&lt;/p&gt;
&lt;p&gt;As a result, with certain mac_do rules, it is possible for a credential switch to incorrectly set the primary group ID to the ID stored in the first element of the original credential&amp;#39;s supplementary group array.&lt;/p&gt;
&lt;p&gt;If the list of supplementary groups is empty, this value will be 0, corresponding to the &amp;#34;wheel&amp;#34; group.  For example, a rule such as &amp;#34;uid=1001&amp;gt;uid=1002&amp;#34; can be abused to set the primary group ID to 0 even if the process did not originally belong to group 0.&lt;/p&gt;
&lt;p&gt;Certain mac_do rules can be abused to set a process&amp;#39; group ID to 0.  Note however, that the rule must apply to the caller in order for the bug to be triggered, e.g., given the ruleset &amp;#34;uid=1001&amp;gt;uid=1002&amp;#34;, the user must have user ID 1001 in order to trigger the bug.&lt;/p&gt;
&lt;p&gt;Further, logged-in users will in general have a non-empty supplementary group list, in which case the bug can at worst be used to set the cred…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-58092</guid>
    </item>
    <item>
      <title>GHSA-ffp5-8472-58q5</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-ffp5-8472-58q5</link>
      <description>&lt;p&gt;In FreeBSD 15.0, the kernel structure used to represent user credentials changed: previously the primary group ID was stored in the first element of the array containing the list of supplementary group IDs, whereas now the primary group ID is stored in a dedicated field.  This change was largely internal to the kernel and not user-visible.&lt;/p&gt;
&lt;p&gt;One function, group_is_primary(), was not properly updated as a part of this transition.  This function is used by mac_do to determine the primary group ID of the credential after applying a transition rule, used when the rule target does not explicitly specify a group.&lt;/p&gt;
&lt;p&gt;As a result, with certain mac_do rules, it is possible for a credential switch to incorrectly set the primary group ID to the ID stored in the first element of the original credential&amp;#39;s supplementary group array.&lt;/p&gt;
&lt;p&gt;If the list of supplementary groups is empty, this value will be 0, corresponding to the &amp;#34;wheel&amp;#34; group.  For example, a rule such as &amp;#34;uid=1001&amp;gt;uid=1002&amp;#34; can be abused to set the primary group ID to 0 even if the process did not originally belong to group 0.&lt;/p&gt;
&lt;p&gt;Certain mac_do rules can be abused to set a process&amp;#39; group ID to 0.  Note however, that the rule must apply to the caller in order for the bug to be triggered, e.g., given the ruleset &amp;#34;uid=1001&amp;gt;uid=1002&amp;#34;, the user must have user ID 1001 in order to trigger the bug.&lt;/p&gt;
&lt;p&gt;Further, logged-in users will in general have a non-empty supplementary group list, in which case the bug can at worst be used to set the cred…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In FreeBSD 15.0, the kernel structure used to represent user credentials changed: previously the primary group ID was stored in the first element of the array containing the list of supplementary group IDs, whereas now the primary group ID is stored in a dedicated field.  This change was largely internal to the kernel and not user-visible.&lt;/p&gt;
&lt;p&gt;One function, group_is_primary(), was not properly updated as a part of this transition.  This function is used by mac_do to determine the primary group ID of the credential after applying a transition rule, used when the rule target does not explicitly specify a group.&lt;/p&gt;
&lt;p&gt;As a result, with certain mac_do rules, it is possible for a credential switch to incorrectly set the primary group ID to the ID stored in the first element of the original credential&amp;#39;s supplementary group array.&lt;/p&gt;
&lt;p&gt;If the list of supplementary groups is empty, this value will be 0, corresponding to the &amp;#34;wheel&amp;#34; group.  For example, a rule such as &amp;#34;uid=1001&amp;gt;uid=1002&amp;#34; can be abused to set the primary group ID to 0 even if the process did not originally belong to group 0.&lt;/p&gt;
&lt;p&gt;Certain mac_do rules can be abused to set a process&amp;#39; group ID to 0.  Note however, that the rule must apply to the caller in order for the bug to be triggered, e.g., given the ruleset &amp;#34;uid=1001&amp;gt;uid=1002&amp;#34;, the user must have user ID 1001 in order to trigger the bug.&lt;/p&gt;
&lt;p&gt;Further, logged-in users will in general have a non-empty supplementary group list, in which case the bug can at worst be used to set the cred…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-ffp5-8472-58q5</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3034 — FreeBSD Project FreeBSD OS: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3034</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in FreeBSD Project FreeBSD OS ausnutzen, um Berechtigungen zu erweitern und möglicherweise Root-Rechte zu erlangen, Sicherheitsmaßnahmen zu umgehen, beliebigen Code auszuführen, Daten zu manipulieren oder offenzulegen oder Denial-of-Service-Zustände herbeizuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in FreeBSD Project FreeBSD OS ausnutzen, um Berechtigungen zu erweitern und möglicherweise Root-Rechte zu erlangen, Sicherheitsmaßnahmen zu umgehen, beliebigen Code auszuführen, Daten zu manipulieren oder offenzulegen oder Denial-of-Service-Zustände herbeizuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3034</guid>
    </item>
  </channel>
</rss>
