CVE-2026-48749

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.8%, top 46% 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
Elevated
9.9EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.9Exploit: Elevated riskExposed: 0

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

Incus is a system container and virtual machine manager. Prior to version 7.2.0, a specially crafted image can be used to read or create/write arbitrary files on the host; possibly leading to arbitrary command execution. Version 7.2.0 fixes the issue.

CVSS v3
9.9
EG Score
9.9(medium)
EG Risk
61(Track*)
EG Risk 61/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
Severity99% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
1%
EPSS %ILE
54%
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 read+write on host via rootfs/ symlink in malicious image · Advisory · lxc/incus · GitHub

https://github.com/lxc/incus/security/advisories/GHSA-2q3f-q5pq-g8wv

Vendor Advisories for CVE-2026-48749(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)
PackageVulnerable rangeFixed inDependents
github.com/lxc/incus
github.com/lxc/incus/v6
github.com/lxc/incus/v77.2.0
github.com/lxc/incus/v7/cmd/incusd7.2.0
Debian:13(2)
PackageVulnerable rangeFixed inDependents
incus6.0.4-2 ... 6.0.4-2+deb13u7~bpo12+1 (15 versions)6.0.4-2+deb13u8
lxd5.0.2+git20231211.1364ae4-9 ... 5.0.2+git20231211.1364ae4-9+deb13u6 (7 versions)5.0.2+git20231211.1364ae4-9+deb13u7
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 ... 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 5× in last 7d / 7× 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.

  1. 2026-08-23 00:51 UTCEG score recompute
  2. 2026-08-23 00:19 UTCEPSS rescore
  3. 2026-08-21 16:28 UTCEG score recompute
  4. 2026-08-21 15:56 UTCEG score recompute
  5. 2026-08-21 15:21 UTCEG score recompute
  6. 2026-07-30 13:23 UTCEG score recompute
  7. 2026-07-26 14:33 UTCEG score recompute
  8. 2026-07-23 03:18 UTCEG score recompute
  9. 2026-06-26 18:39 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-48749?
CVE-2026-48749 is a critical vulnerability published on June 26, 2026. Incus is a system container and virtual machine manager. Prior to version 7.2.0, a specially crafted image can be used to read or create/write arbitrary files on the host; possibly leading to arbitrary command execution. Version 7.2.0 fixes the issue.
When was CVE-2026-48749 disclosed?
CVE-2026-48749 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-48749 actively exploited?
CVE-2026-48749 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 45.9% of all scored CVEs.
What is the CVSS score of CVE-2026-48749?
CVE-2026-48749 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2026-48749?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48749, 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-48749

Explore →

Is Your Infrastructure Affected by CVE-2026-48749?

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