CVE-2026-102631

MediumCVSS 5.9

Published: 15/10/2026(UTC)Translated: 15/10/2026(UTC)NVD NIST

Summary

Risk Assessment

The new user can access and modify files belonging to the previous user, including credentials such as SSH keys and cloud API tokens, and the local account record is silently rebound to the new identity.

Recommendation

Upgrade authd to version 0.7.1 or later; as a mitigation, administrators should lock or delete the previous user's local authd account when the corresponding IdP account is removed.

Other vulnerabilities in authd

CVE-2026-6970High
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's primary GID differs from their UID, authd incorrectly resets the GID to the UID upon next login, causing newly created files and directories to be owned by the wrong group, leading to denial of service and potential privilege escalation.

Original NVD description (English source)

In authd before 0.7.1, the user identity matching in UpdateUser (internal/users/manager.go) resolves an incoming login by the broker-scoped provider ID, but falls back to matching the username when the provider ID does not belong to any known user, and does not reject a conflicting non-empty provider ID. If an identity provider reassigns an email address, which authd uses as the username, to a new account, the new account inherits the previous user's local UID and home directory on its next login. This allows the new user to access and modify files belonging to the previous user, including credentials such as SSH keys and cloud API tokens, and silently rebinds the local account record to the new identity. As a mitigation, administrators should lock or delete the previous user's local authd account when the corresponding IdP account is removed.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS