GitHub Advisoryadvisory · Go

GHSA-fg3j-5w9g-hmg7 authd: Primary group ID is incorrectly set to value of UID

HIGH Published 2026-05-05 Modified 2026-05-05 Official page ↗
Aliases
CVE-2026-6970
Ecosystem
Go
Packages
github.com/canonical/authd
Severity
High
CVSS vector
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Weaknesses
CWE-842
Reviewed
2026-05-05

Affected packages

• Go github.com/canonical/authd: >= 0.6.0, < 0.6.4 → fixed in 0.6.4

Description

authd 0.6.0 contains a bug which can lead to an incorrect primary group ID. 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: 1. The user was created with authd &2 continue fi if [ "$OLD_GID" = "$GID" ]; then continue # user not affected fi USER_HOME=$(getent passwd "$user" | cut -d: -f6) echo "Fixing $user: resetting GID from $OLD_GID to $GID" sudo authctl group set-gid "$user" "$OLD_GID" sudo authctl group set-gid "$user" "$GID" sudo chown -R --from=":$OLD_GID" ":$GID" "$USER_HOME" done ``` After applying the fix, affected users must log out and log back in for `id`, `groups`, and new file GID stamping to reflect the corrected primary group. You may also optionally terminate a user's active session with: ```bash sudo loginctl terminate-user "$user" ``` If the users also own files outside their home directory, the ownership of those files might have to be updated as well. Fixed by: https://github.com/canonical/authd/commit/154b428305cb1a7a19c897626fefd09d6dde8b9f

Related

Alias · CVE (1)

  • CVE-2026-6970 authd prior to version 0.6.4 contains a logic error in primary group ID assignment that can lead to local privilege escalation. vulnerability

Weakness · CWE (1)

  • CWE-842 Placement of User into Incorrect Group weakness

References