---
id: CVE-2026-102631
title: >-
  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 …
summary: >-
  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 …
severity: medium
cvss: 5.9
cvssVector: 'CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N'
cwe:
  - CWE-287
vendor: Canonical
product: authd
affected:
  - authd >= 0.1 < 0.7.1
  - authd >= 0.1 < 0.7.1~ubuntu24.04.1
  - authd >= 0.1 < 0.7.1~ubuntu26.04
published: '2026-10-15'
updated: '2026-10-15'
sourceUpdated: '2026-10-15T17:17:10.130'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-102631'
references:
  - url: 'https://bugs.launchpad.net/ubuntu/+source/authd/+bug/2168531'
    label: security@ubuntu.com
  - url: 'https://github.com/canonical/authd/pull/2067'
    label: security@ubuntu.com
  - url: 'https://ubuntu.com/security/CVE-2026-102631'
    label: security@ubuntu.com
tags:
  - nvd
  - cve.org
cvssSource: cna
ingestedAt: '2026-10-15T17:18:20.097Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.