Incus is a system container and virtual machine manager. Prior to version 7.2.0, an arbitrary file write exists in the Incus client when a malicious image server returns a crafted Incus-Image-Hash header. This can lead to arbitrary command execution as root on the server. Version 7.2.0 patches the issue.
CVE-2026-48769
CRITICALPre-NVD 9.99.9—
EchelonGraph scoreMEDIUM confidence
This critical-severity CVE scores 9.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 63% 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, secondary
9.9EG
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.9Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.9
- EG Score
- 9.9(medium)
- EG Risk
- 49(Track)EG Risk 49/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 computedSeverity99% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 37%
- KEV
- Not listed
Published
June 26, 2026
Last Modified
August 21, 2026
Advisory Details (1)
Auto-updated Aug 21, 2026🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available
Arbitrary file write on client due to trusted image hash · Advisory · lxc/incus · GitHub
https://github.com/lxc/incus/security/advisories/GHSA-f6m5-xw2g-xc4xVendor Advisories for CVE-2026-48769(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(8 across 4 ecosystems)
Go(4)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/lxc/incus | — | — | — |
| github.com/lxc/incus/v6 | — | — | — |
| github.com/lxc/incus/v7 | — | 7.2.0 | — |
| github.com/lxc/incus/v7/cmd/incusd | — | 7.2.0 | — |
Debian:13(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| incus | 6.0.4-2 ... 6.0.4-2+deb13u7~bpo12+1 (15 versions) | 6.0.4-2+deb13u8 | — |
| lxd | 5.0.2+git20231211.1364ae4-9 ... 5.0.2+git20231211.1364ae4-9+deb13u6 (7 versions) | 5.0.2+git20231211.1364ae4-9+deb13u7 | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| lxd | 5.0.2+git20231211.1364ae4-1 ... 5.0.2-6 (17 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| incus | 6.0.4-2 ... 7.0.0-5~bpo13+1 (28 versions) | 7.0.0-5 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 5× 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.
- 2026-08-23 00:56 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 15:21 UTCEG score recompute
- 2026-07-30 13:22 UTCEG score recompute
- 2026-07-26 14:33 UTCEG score recompute
- 2026-07-23 03:18 UTCEG score recompute
- 2026-06-26 19:37 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-20
- CVE-2005-0050EG 10.0EPSS p99HIGH
- CVE-2004-1019EG 10.0EPSS p94HIGH
- CVE-2004-0840EG 10.0EPSS p98HIGH
- CVE-2003-1425EG 10.0EPSS p96HIGH
- CVE-2003-1487EG 10.0EPSS p94HIGH
- CVE-2002-1874EG 10.0HIGH
- CVE-2002-2236EG 10.0EPSS p91HIGH
- CVE-2002-2365EG 10.0HIGH
- CVE-2002-1358EG 10.0EPSS p93HIGH
- CVE-2002-1359EG 10.0EPSS p100HIGH
Frequently asked(5)
What is CVE-2026-48769?
CVE-2026-48769 is a critical vulnerability published on June 26, 2026. Incus is a system container and virtual machine manager. Prior to version 7.2.0, an arbitrary file write exists in the Incus client when a malicious image server returns a crafted Incus-Image-Hash header. This can lead to arbitrary command execution as root on the server. Version 7.2.0 patches the…
When was CVE-2026-48769 disclosed?
CVE-2026-48769 was first published in the National Vulnerability Database on June 26, 2026, with the most recent update on August 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48769 actively exploited?
CVE-2026-48769 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 63.2% of all scored CVEs.
What is the CVSS score of CVE-2026-48769?
CVE-2026-48769 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2026-48769?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48769, 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-48769
Is Your Infrastructure Affected by CVE-2026-48769?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.