CVE-2026-6970

HIGHNVD 7.37.3—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.3 under NVD CVSS v3. EPSS exploit probability: 0.0%, top 96% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.3
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.3Exploit: NoneExposed: 0

A fix is available — apply it.

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 group ID (GID) differs from their UID, either because the account was created with authd prior to version 0.5.4 or because the primary group was manually changed via the authctl group set-gid command, and the user's identity provider record is updated, authd incorrectly resets the user's primary group ID to their UID upon next login. This causes newly created files and directories to be owned by the wrong group, causing denial of service issues, and potentially granting unintended access to other local users and allowing local privilege escalation.

CVSS v3
7.3
EG Score
7.3(medium)
EPSS
1.5%
KEV
Not listed

Published

April 27, 2026

Last Modified

April 27, 2026

Advisory Details (2)

Auto-updated Jun 11, 2026
Patch available. Sources: github_commit, github.
github Patch Available

Primary group ID incorrectly set to value of UID · Advisory · canonical/authd · GitHub

https://github.com/canonical/authd/security/advisories/GHSA-fg3j-5w9g-hmg7
github_commit

commit 154b428305cb (canonical/authd)

Fix landed in canonical/authd commit 154b428305cb — awaiting tagged release

https://github.com/canonical/authd/commit/154b428305cb1a7a19c897626fefd09d6dde8b9f

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuauthd (0.6.1ubuntu0.1) @ resolute2026-06-14ubuntu

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.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/canonical/authd—0.6.4—

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 9× in last 7d / 34× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 103 total refreshes for this CVE.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:25 UTCEPSS rescore
  4. 2026-07-21 15:25 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-20 13:04 UTCOSV refresh
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-18 10:04 UTCEPSS rescore
  9. 2026-07-16 17:03 UTCEPSS rescore
  10. 2026-07-15 16:57 UTCEPSS rescore
  11. 2026-07-15 02:00 UTCEPSS rescore
  12. 2026-07-13 22:31 UTCEPSS rescore
  13. 2026-07-12 05:46 UTCEPSS rescore
  14. 2026-07-11 08:27 UTCEPSS rescore
  15. 2026-07-11 08:27 UTCEPSS rescore
  16. 2026-07-09 19:10 UTCEPSS rescore
  17. 2026-07-09 19:10 UTCEPSS rescore
  18. 2026-07-08 15:16 UTCEPSS rescore
  19. 2026-07-08 15:16 UTCEPSS rescore
  20. 2026-07-07 13:46 UTCEPSS rescore
  21. 2026-07-07 13:46 UTCEPSS rescore
  22. 2026-07-06 02:23 UTCEPSS rescore
  23. 2026-07-06 02:23 UTCEPSS rescore
  24. 2026-07-05 02:31 UTCEPSS rescore
  25. 2026-07-05 02:30 UTCEPSS rescore
Show 75 more
  1. 2026-07-04 06:31 UTCEPSS rescore
  2. 2026-07-04 06:31 UTCEPSS rescore
  3. 2026-07-01 15:07 UTCEPSS rescore
  4. 2026-06-30 23:22 UTCEPSS rescore
  5. 2026-06-29 14:06 UTCEPSS rescore
  6. 2026-06-28 14:07 UTCEPSS rescore
  7. 2026-06-27 03:08 UTCEPSS rescore
  8. 2026-06-24 14:05 UTCEPSS rescore
  9. 2026-06-23 21:33 UTCEPSS rescore
  10. 2026-06-21 14:56 UTCEPSS rescore
  11. 2026-06-21 14:56 UTCEPSS rescore
  12. 2026-06-21 01:59 UTCEPSS rescore
  13. 2026-06-21 01:59 UTCEPSS rescore
  14. 2026-06-19 19:26 UTCEPSS rescore
  15. 2026-06-19 19:26 UTCEPSS rescore
  16. 2026-06-18 17:52 UTCEPSS rescore
  17. 2026-06-18 17:52 UTCEPSS rescore
  18. 2026-06-17 17:53 UTCEPSS rescore
  19. 2026-06-16 17:53 UTCEPSS rescore
  20. 2026-06-15 17:49 UTCEPSS rescore
  21. 2026-06-15 17:49 UTCEPSS rescore
  22. 2026-06-14 23:18 UTCEPSS rescore
  23. 2026-06-14 22:46 UTCVendor advisory
  24. 2026-06-14 11:03 UTCVendor advisory
  25. 2026-06-13 23:00 UTCEPSS rescore
  26. 2026-06-12 23:12 UTCEPSS rescore
  27. 2026-06-12 23:12 UTCEPSS rescore
  28. 2026-06-12 10:42 UTCVendor advisory
  29. 2026-06-11 21:34 UTCVendor advisory
  30. 2026-06-11 14:00 UTCEPSS rescore
  31. 2026-06-11 10:08 UTCVendor advisory
  32. 2026-06-10 22:36 UTCVendor advisory
  33. 2026-06-10 22:19 UTCEPSS rescore
  34. 2026-06-10 13:22 UTCEPSS rescore
  35. 2026-06-10 11:07 UTCVendor advisory
  36. 2026-06-09 23:40 UTCVendor advisory
  37. 2026-06-09 11:38 UTCVendor advisory
  38. 2026-06-09 00:11 UTCVendor advisory
  39. 2026-06-08 14:17 UTCEPSS rescore
  40. 2026-06-08 07:03 UTCVendor advisory
  41. 2026-06-07 19:36 UTCVendor advisory
  42. 2026-06-07 15:25 UTCEPSS rescore
  43. 2026-06-07 08:10 UTCVendor advisory
  44. 2026-06-06 20:44 UTCVendor advisory
  45. 2026-06-06 13:47 UTCEPSS rescore
  46. 2026-06-06 09:16 UTCVendor advisory
  47. 2026-06-05 22:47 UTCEPSS rescore
  48. 2026-06-05 21:48 UTCVendor advisory
  49. 2026-06-05 10:21 UTCVendor advisory
  50. 2026-06-05 06:10 UTCEPSS rescore
  51. 2026-06-04 22:03 UTCVendor advisory
  52. 2026-06-04 13:12 UTCEPSS rescore
  53. 2026-06-04 10:28 UTCVendor advisory
  54. 2026-06-03 22:19 UTCVendor advisory
  55. 2026-06-03 10:36 UTCVendor advisory
  56. 2026-06-02 22:39 UTCVendor advisory
  57. 2026-06-02 20:13 UTCEPSS rescore
  58. 2026-06-02 11:12 UTCVendor advisory
  59. 2026-06-01 23:07 UTCVendor advisory
  60. 2026-06-01 13:52 UTCEPSS rescore
  61. 2026-06-01 11:39 UTCVendor advisory
  62. 2026-05-31 22:30 UTCEPSS rescore
  63. 2026-05-31 22:30 UTCEPSS rescore
  64. 2026-05-31 00:16 UTCEPSS rescore
  65. 2026-05-31 00:16 UTCEPSS rescore
  66. 2026-05-29 13:44 UTCEPSS rescore
  67. 2026-05-29 13:44 UTCEPSS rescore
  68. 2026-05-28 13:44 UTCEPSS rescore
  69. 2026-05-28 13:44 UTCEPSS rescore
  70. 2026-05-27 13:40 UTCEPSS rescore
  71. 2026-05-27 13:40 UTCEPSS rescore
  72. 2026-05-26 13:44 UTCEPSS rescore
  73. 2026-05-26 07:18 UTCEPSS rescore
  74. 2026-05-21 22:43 UTCEPSS rescore
  75. 2026-05-20 22:38 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-6970?
CVE-2026-6970 is a high vulnerability published on April 27, 2026. 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 group ID (GID) differs from their UID, either because the account was created with authd prior to version 0.5.4 or because the primary group was…
When was CVE-2026-6970 disclosed?
CVE-2026-6970 was first published in the National Vulnerability Database on April 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-6970 actively exploited?
CVE-2026-6970 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-6970?
CVE-2026-6970 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-6970?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6970, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-6970

Explore →

Is Your Infrastructure Affected by CVE-2026-6970?

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

Start Free Scan →Browse All CVEs