CVE-2026-6970 — authd
Fix: canonical/authd@154b428CVE-2026-6970 is a CWE-842 vulnerability in github.com/canonical/authd. A fix is available for github.com/canonical/authd — see the affected versions and patch details below.
authd Denial of Service and Local Privilege Escalation
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-6970.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
github.com/canonical/authdReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
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:
-
The user was created with authd < 0.5.4 (released June 2025). Those users were created with UID != GID.
-
The primary group of the user was modified manually with the authctl utility that is shipped with authd (
authctl group set-gid).
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.
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't have.
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:
authd_users=$(getent passwd --service authd | cut -d: -f1)
for user in $authd_users; do
OLD_GID=$(id -g "$user")
GID=$(getent group "$user" | cut -d: -f3)
if [ -z "$GID" ]; then
echo "Warning: could not determine GID for $user, skipping" >&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:
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/canonical/authd | ≥ 0.6.0&&< 0.6.4 | 0.6.4go get github.com/canonical/authd@v0.6.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/canonical/authd, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/canonical/authd to 0.6.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-6970 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2026-6970 in your dependencies?
Find it across Go, including transitive dependencies.