CVE-2026-34179

CRITICALNVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-04-10. NVD baseline CVSS 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In Canonical LXD versions 4.12 through 6.7, the doCertificateUpdate function in lxd/certificates.go does not validate the Type field when handling PUT/PATCH requests to /1.0/certificates/{fingerprint} for restricted TLS certificate users, allowing a remote authenticated attacker to escalate privileges to cluster admin.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
57(Track*)
EG Risk 57/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

April 9, 2026

Last Modified

April 22, 2026

Advisory Details (2)

Auto-updated Aug 1, 2026
🔬 Proof of concept available. Patch available. Sources: github_pr, github.
github Patch Available🟡 PoC Available

Update of type field in restricted TLS certificate allows privilege escalation to cluster admin · Advisory · canonical/lxd · GitHub

https://github.com/canonical/lxd/security/advisories/GHSA-c3h3-89qf-jqm5
github_pr

Improve validation on certificate edit

Fix merged in canonical/lxd PR #17936 on 2026-03-23 — awaiting tagged release

https://github.com/canonical/lxd/pull/17936

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
gogithub.com/canonical/lxd—ghsa

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

(5 across 4 ecosystems)
Debian:13(2)
PackageVulnerable rangeFixed inDependents
incus6.0.4-2 ... 6.0.4-2+deb13u6~bpo12+1 (12 versions)6.0.4-2+deb13u6—
lxd5.0.2+git20231211.1364ae4-9, 5.0.2+git20231211.1364ae4-9+deb13u1, 5.0.2+git20231211.1364ae4-9+deb13u2, 5.0.2+git20231211.1364ae4-9+deb13u3, 5.0.2+git20231211.1364ae4-9+deb13u45.0.2+git20231211.1364ae4-9+deb13u5—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
lxd5.0.2+git20231211.1364ae4-1 ... 5.0.2-6 (17 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
incus6.0.4-2 ... 6.0.6-2 (12 versions)6.0.6-3—
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/canonical/lxd———

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 30× 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 226 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-34179?
CVE-2026-34179 is a critical vulnerability published on April 9, 2026. In Canonical LXD versions 4.12 through 6.7, the doCertificateUpdate function in lxd/certificates.go does not validate the Type field when handling PUT/PATCH requests to /1.0/certificates/{fingerprint} for restricted TLS certificate users, allowing a remote authenticated attacker to escalate…
When was CVE-2026-34179 disclosed?
CVE-2026-34179 was first published in the National Vulnerability Database on April 9, 2026, with the most recent update on April 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-34179 actively exploited?
CVE-2026-34179 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 80.3% of all scored CVEs.
What is the CVSS score of CVE-2026-34179?
CVE-2026-34179 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-34179?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-34179, 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-34179

Explore →

Is Your Infrastructure Affected by CVE-2026-34179?

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

Start Free Scan →Browse All CVEs