Incus is a system container and virtual machine manager. Prior to version 7.2.0, the record-output parameter of the /instances/$name/exec endpoint stores the output of the command in the exec-output directory of the instance. If exec-output is a symlink, file named exec_UUID.stdout and exec_UUID.stderr can be written to an arbitrary location where the .stdout file will contain arbitrary content. This behavior can be abused for arbitrary command execution. Version 7.2.0 contains a patch.
CVE-2026-48750
This critical-severity CVE scores 9.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.8%, top 47% 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).
- High severity, but no confirmed exploitation yet
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%Exploitation1% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 53%
- KEV
- Not listed
Published
June 26, 2026
Last Modified
August 21, 2026
Advisory Details (1)
Auto-updated Aug 21, 2026Arbitrary file write on host via `exec-output` symlink in crafted image · Advisory · lxc/incus · GitHub
https://github.com/lxc/incus/security/advisories/GHSA-73hr-m85f-64v9Vendor Advisories for CVE-2026-48750(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 01:31 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 15:21 UTCEG score recompute
- 2026-07-30 13:36 UTCEG score recompute
- 2026-07-26 14:33 UTCEG score recompute
- 2026-07-23 03:18 UTCEG score recompute
- 2026-06-26 18:39 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-73
- CVE-2022-24900EG 9.9EPSS p95CRITICAL
- CVE-2020-37080EG 9.8CRITICAL
- CVE-2023-4634EG 9.8EPSS p100CRITICAL
- CVE-2023-4191EG 9.8CRITICAL
- CVE-2022-39952EG 9.8EPSS p100CRITICAL
- CVE-2014-125059NVD 5.0EG 9.8CRITICAL
- CVE-2014-125044NVD 6.3EG 9.8CRITICAL
- CVE-2022-45213NVD 5.3EG 9.8CRITICAL
- CVE-2021-38477EG 9.8CRITICAL
- CVE-2020-1631NVD 8.8EG 9.8 KEVEPSS p91CRITICAL
Frequently asked(5)
What is CVE-2026-48750?
When was CVE-2026-48750 disclosed?
Is CVE-2026-48750 actively exploited?
What is the CVSS score of CVE-2026-48750?
How do I remediate CVE-2026-48750?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-48750
Is Your Infrastructure Affected by CVE-2026-48750?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.