CVE-2026-102631

MEDIUMPre-NVD 5.95.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 5.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (1st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-102198 (ENISA EUVD) · GHSA-92hm-xx6p-hch9 (GitHub Security Advisories)Source: ENISA EUVD

5.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 5.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
5.9
EG Score
5.9MEDIUMmedium confidence
EG Risk
27
EG Risk 27/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity59% × 45%
Impact severity (EG Severity): CVSS 5.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.9): severity, escalated by confirmed exploitation. This CVE's 5.9 is its impact severity (EG Severity), not escalated.

EG Severity
5.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 15, 2026

Last Modified

October 16, 2026

Advisory Details (1)

Auto-updated Oct 15, 2026
Patch available. Sources: github_pr.
GitHub pull request

Prevent recycled usernames from inheriting existing accounts

Fix merged in canonical/authd PR #2067 on 2026-10-08 — awaiting tagged release

https://github.com/canonical/authd/pull/2067

Vendor Advisories for CVE-2026-102631(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuauthd (0.7.1) @ stonking2026-10-29ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 10× in last 7d / 30× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  2. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  3. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  4. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  5. 2026-10-29 14:49 UTCEG score recompute
  6. 2026-10-29 14:49 UTCVendor advisory
  7. 2026-10-29 14:49 UTCGHSA enrichmentGHSA-92hm-xx6p-hch9
  8. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  9. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  10. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  11. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  12. 2026-10-25 14:56 UTCEG score recompute
  13. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  14. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  15. 2026-10-23 09:28 UTCEG score recompute
  16. 2026-10-23 09:28 UTCGHSA enrichmentGHSA-92hm-xx6p-hch9
  17. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  18. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  19. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  20. 2026-10-18 05:10 UTCEG score recompute
  21. 2026-10-16 21:45 UTCEG score recompute
  22. 2026-10-16 21:45 UTCGHSA enrichmentGHSA-92hm-xx6p-hch9
  23. 2026-10-16 20:23 UTCEG score recompute
  24. 2026-10-16 20:23 UTCGHSA enrichmentGHSA-92hm-xx6p-hch9
  25. 2026-10-16 20:13 UTCEG score recompute
Show 5 more
  1. 2026-10-16 20:13 UTCGHSA enrichmentGHSA-92hm-xx6p-hch9
  2. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  3. 2026-10-15 17:30 UTCEG score recompute
  4. 2026-10-15 16:49 UTCEG score recomputeFirst assessed: 5.9 MEDIUM
  5. 2026-10-15 16:47 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-102631?
CVE-2026-102631 is a medium-severity vulnerability; its CVE record was published on October 15, 2026. 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…
When was the CVE record for CVE-2026-102631 published?
The CVE record for CVE-2026-102631 was published on October 15, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 16, 2026; the record at its source may have been updated since.
Is CVE-2026-102631 actively exploited?
CVE-2026-102631 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-102631?
CVE-2026-102631 has a CVSS base score of 5.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-102631?
A fix for CVE-2026-102631 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-102631 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-102631

Explore →

Is Your Infrastructure Affected by CVE-2026-102631?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs