CVE-2026-28384

CRITICALNVD 9.99.9
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.9 under NVD CVSS v3. EPSS exploit probability: 0.7% (53rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated

Also known asEUVD-2026-11585 (ENISA EUVD)Source: ENISA EUVD

9.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.9Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

An improper sanitization of the compression_algorithm parameter in Canonical LXD allows an authenticated, unprivileged user to execute commands as the LXD daemon on the LXD server via API calls to the image and backup endpoints. This issue affected LXD from 4.12 through 6.6 and was fixed in the snap versions 5.0.6-e49d9f4 (channel 5.0/stable), 5.21.4-1374f39 (channel 5.21/stable), and 6.7-1f11451 (channel 6.0 stable). The channel 4.0/stable is not affected as it contains version 4.0.10.

CVSS v3
9.9
EG Score
9.9CRITICALmedium confidence
EG Risk
76
EG Risk 76/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)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
53rd
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 (9.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

EG Severity
9.9 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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 low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days 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 low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (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

March 12, 2026

Last Modified

September 18, 2026

Advisory Details (4)

Auto-updated Oct 30, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Authenticated host RCE via unsanitized compression_algorithm in image and backup API endpoints · Advisory · canonical/lxd · GitHub

Affected: 5.21.4-1374f39 (2026-03-11)

https://github.com/canonical/lxd/security/advisories/GHSA-4rmf-rcp8-2r9g
GitHub commit

commit 7046979645c2 (canonical/lxd)

Fix landed in canonical/lxd commit 7046979645c2 — awaiting tagged release

https://github.com/canonical/lxd/commit/7046979645c2ce1b63b2f9e60ddf6cbc4c4b78f9
GitHub commit

commit 043696a13171 (canonical/lxd)

Fix landed in canonical/lxd commit 043696a13171 — awaiting tagged release

https://github.com/canonical/lxd/commit/043696a13171ace7dd4c2b32d34ce039ab629052
Web page

LXD Authenticated Remote Code Execution fixes available - News - Ubuntu Discourse

https://discourse.ubuntu.com/t/lxd-authenticated-remote-code-execution-fixes-available/78365

Affected Packages

(4 across 3 ecosystems)
Debian:13(2)
PackageVulnerable rangeFix by version rangeDependents
incus6.0.4-2 ... 6.0.4-2+deb13u4~bpo12+1 (9 versions)
  • every version up to 6.0.4-2+deb13u5: fixed in 6.0.4-2+deb13u5
—
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
  • every version up to 5.0.2+git20231211.1364ae4-9+deb13u4: fixed in 5.0.2+git20231211.1364ae4-9+deb13u4
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
lxd5.0.2-5, 5.0.2-5+deb12u1, 5.0.2-5+deb12u2, 5.0.2-5+deb12u3
  • every version on: no fix on record
  • every version up to 5.0.2-5+deb12u4: fixed in 5.0.2-5+deb12u4
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
incus6.0.4-2 ... 6.0.5-8 (10 versions)
  • every version up to 6.0.6-1: fixed in 6.0.6-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 54× 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.

Showing the most recent 95 of 124 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 29 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  2. 2026-11-01 18:01 UTCEG score recompute
  3. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  4. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  5. 2026-10-31 15:54 UTCEG score recompute
  6. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  7. 2026-10-30 13:46 UTCEG score recompute
  8. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  9. 2026-10-29 11:30 UTCEG score recompute
  10. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  11. 2026-10-28 09:23 UTCEG score recompute
  12. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  13. 2026-10-27 06:35 UTCEG score recompute
  14. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  15. 2026-10-26 00:43 UTCEG score recompute
  16. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  17. 2026-10-25 14:38 UTCEG score recompute
  18. 2026-10-24 22:33 UTCEG score recompute
  19. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  20. 2026-10-23 20:26 UTCEG score recompute
  21. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  22. 2026-10-22 18:18 UTCEG score recompute
  23. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  24. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  25. 2026-10-21 16:10 UTCEG score recompute
Show 70 more
  1. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  2. 2026-10-20 14:01 UTCEG score recompute
  3. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  4. 2026-10-19 11:52 UTCEG score recompute
  5. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  6. 2026-10-18 03:50 UTCEG score recompute
  7. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  8. 2026-10-17 04:18 UTCEG score recompute
  9. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  10. 2026-10-16 02:10 UTCEG score recompute
  11. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  12. 2026-10-14 22:01 UTCEG score recompute
  13. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  14. 2026-10-13 17:45 UTCEG score recompute
  15. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  16. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  17. 2026-10-12 15:37 UTCEG score recompute
  18. 2026-10-11 19:59 UTCEG score recompute
  19. 2026-10-11 17:12 UTCEG score recompute
  20. 2026-10-11 14:42 UTCEG score recompute
  21. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  22. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  23. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  24. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  25. 2026-10-08 08:35 UTCOSV refresh
  26. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  27. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  28. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  29. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  30. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  31. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  32. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  33. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  34. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  35. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  36. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  37. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  38. 2026-09-18 14:22 UTCEG score recompute
  39. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  40. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  41. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  42. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  43. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  44. 2026-09-11 15:48 UTCEG score recompute▲ 0.50
  45. 2026-09-11 15:48 UTCNVD updateCVSS v3 → 9.9
  46. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  47. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  48. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  49. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  50. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  51. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  52. 2026-09-02 19:40 UTCOSV refresh
  53. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  54. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  55. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  56. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  57. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  58. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  59. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  60. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  61. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  62. 2026-08-24 14:17 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  63. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  64. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  65. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  66. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  67. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  68. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  69. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  70. 2026-08-16 11:47 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-28384?
CVE-2026-28384 is a critical-severity vulnerability; its CVE record was published on March 12, 2026. An improper sanitization of the compression_algorithm parameter in Canonical LXD allows an authenticated, unprivileged user to execute commands as the LXD daemon on the LXD server via API calls to the image and backup endpoints. This issue affected LXD from 4.12 through 6.6 and was fixed in the…
When was CVE-2026-28384 made public?
CVE-2026-28384 was made public on March 12, 2026: that is the date its CVE record's CNA, Canonical Ltd., gives for when the vulnerability was made public. The CVE record itself was published on March 12, 2026. EchelonGraph's copy of the record carries a last-modified date of September 18, 2026; the record at its source may have been updated since.
Is CVE-2026-28384 actively exploited?
CVE-2026-28384 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-28384?
CVE-2026-28384 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2026-28384?
A fix for CVE-2026-28384 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-28384?

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