<?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>Sat, 03 Oct 2026 03:30:40 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-293170</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-293170</link>
      <description>EUVD-2026-293170</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-293170</guid>
    </item>
    <item>
      <title>fkie_cve-2026-6970</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-6970</link>
      <description>&lt;p&gt;authd prior to version 0.6.4 contains a logic error in primary group ID assignment that can lead to local privilege escalation. When a user&amp;#39;s primary group ID (GID) differs from their UID, either because the account was created with authd prior to version 0.5.4 or because the primary group was manually changed via the `authctl group set-gid` command, and the user&amp;#39;s identity provider record is updated, authd incorrectly resets the user&amp;#39;s primary group ID to their UID upon next login. This causes newly created files and directories to be owned by the wrong group, causing denial of service issues, and potentially granting unintended access to other local users and allowing local privilege escalation.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;authd prior to version 0.6.4 contains a logic error in primary group ID assignment that can lead to local privilege escalation. When a user&amp;#39;s primary group ID (GID) differs from their UID, either because the account was created with authd prior to version 0.5.4 or because the primary group was manually changed via the `authctl group set-gid` command, and the user&amp;#39;s identity provider record is updated, authd incorrectly resets the user&amp;#39;s primary group ID to their UID upon next login. This causes newly created files and directories to be owned by the wrong group, causing denial of service issues, and potentially granting unintended access to other local users and allowing local privilege escalation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-6970</guid>
    </item>
    <item>
      <title>GHSA-fg3j-5w9g-hmg7 — authd: Primary group ID is incorrectly set to value of UID</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-fg3j-5w9g-hmg7</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/canonical/authd&lt;/p&gt;
&lt;p&gt;authd 0.6.0 contains [a bug](https://github.com/canonical/authd/issues/1482) which can lead to an incorrect primary group ID.&lt;/p&gt;
&lt;p&gt;It affects users whose primary group ID (i.e. the GID in the user record) differs from their UID. There are two ways which can lead to this:&lt;/p&gt;
&lt;p&gt;1. The user was created with authd &amp;lt; 0.5.4 (released June 2025). Those users were created with UID != GID.&lt;/p&gt;
&lt;p&gt;2. The primary group of the user was modified manually with the authctl utility that is shipped with authd (`authctl group set-gid`).&lt;/p&gt;
&lt;p&gt;Another condition is that some user information must have changed in the identity provider (else the user record is not updated upon login). If that is the case, the next time an affected user logs in, authd will set their primary group ID to their UID.&lt;/p&gt;
&lt;p&gt;This could lead to local privileges escalation. Also, files and directories created by those users will be owned by that incorrect primary group, which may grant other local users access to those files which they shouldn&amp;#39;t have.&lt;/p&gt;
&lt;p&gt;Users who are affected by the issue can run this script to fix the primary group ID of all authd users and the file ownership of files in the home directory created with the incorrect GID:&lt;/p&gt;
&lt;p&gt;```bash
authd_users=$(getent passwd --service authd | cut -d: -f1)
for user in $authd_users; do
    OLD_GID=$(id -g &amp;#34;$user&amp;#34;)
    GID=$(getent group &amp;#34;$user&amp;#34; | cut -d: -f3)
    if [ -z &amp;#34;$GID&amp;#34; ]; then
        echo &amp;#34;Warning: could not determine GID for $user, skipping&amp;#34; &amp;gt;&amp;amp;2
        continue
    fi
    if [ &amp;#34;$OLD_GID…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/canonical/authd&lt;/p&gt;
&lt;p&gt;authd 0.6.0 contains [a bug](https://github.com/canonical/authd/issues/1482) which can lead to an incorrect primary group ID.&lt;/p&gt;
&lt;p&gt;It affects users whose primary group ID (i.e. the GID in the user record) differs from their UID. There are two ways which can lead to this:&lt;/p&gt;
&lt;p&gt;1. The user was created with authd &amp;lt; 0.5.4 (released June 2025). Those users were created with UID != GID.&lt;/p&gt;
&lt;p&gt;2. The primary group of the user was modified manually with the authctl utility that is shipped with authd (`authctl group set-gid`).&lt;/p&gt;
&lt;p&gt;Another condition is that some user information must have changed in the identity provider (else the user record is not updated upon login). If that is the case, the next time an affected user logs in, authd will set their primary group ID to their UID.&lt;/p&gt;
&lt;p&gt;This could lead to local privileges escalation. Also, files and directories created by those users will be owned by that incorrect primary group, which may grant other local users access to those files which they shouldn&amp;#39;t have.&lt;/p&gt;
&lt;p&gt;Users who are affected by the issue can run this script to fix the primary group ID of all authd users and the file ownership of files in the home directory created with the incorrect GID:&lt;/p&gt;
&lt;p&gt;```bash
authd_users=$(getent passwd --service authd | cut -d: -f1)
for user in $authd_users; do
    OLD_GID=$(id -g &amp;#34;$user&amp;#34;)
    GID=$(getent group &amp;#34;$user&amp;#34; | cut -d: -f3)
    if [ -z &amp;#34;$GID&amp;#34; ]; then
        echo &amp;#34;Warning: could not determine GID for $user, skipping&amp;#34; &amp;gt;&amp;amp;2
        continue
    fi
    if [ &amp;#34;$OLD_GID…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-fg3j-5w9g-hmg7</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-6970</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-6970</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:26.04:LTS: authd&lt;/p&gt;
&lt;p&gt;authd prior to version 0.6.4 contains a logic error in primary group ID assignment that can lead to local privilege escalation. When a user&amp;#39;s primary group ID (GID) differs from their UID, either because the account was created with authd prior to version 0.5.4 or because the primary group was manually changed via the `authctl group set-gid` command, and the user&amp;#39;s identity provider record is updated, authd incorrectly resets the user&amp;#39;s primary group ID to their UID upon next login. This causes newly created files and directories to be owned by the wrong group, causing denial of service issues, and potentially granting unintended access to other local users and allowing local privilege escalation.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:26.04:LTS: authd&lt;/p&gt;
&lt;p&gt;authd prior to version 0.6.4 contains a logic error in primary group ID assignment that can lead to local privilege escalation. When a user&amp;#39;s primary group ID (GID) differs from their UID, either because the account was created with authd prior to version 0.5.4 or because the primary group was manually changed via the `authctl group set-gid` command, and the user&amp;#39;s identity provider record is updated, authd incorrectly resets the user&amp;#39;s primary group ID to their UID upon next login. This causes newly created files and directories to be owned by the wrong group, causing denial of service issues, and potentially granting unintended access to other local users and allowing local privilege escalation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-6970</guid>
    </item>
  </channel>
</rss>
