CVE-2026-48754

LOWPre-NVD 2.12.1—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 2.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 79% 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
2.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 2.1Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Incus is a system container and virtual machine manager. Prior to version 7.1.0, (*backend).createDependentVolumesFromBackup in internal/server/storage/backend.go contains a cluster of unguarded pointer derefs on every dependent-volume entry's VolumeSnapshots[i], Volume, and Pool sub-fields. An authenticated user with can_create_instances permission on any project can crash the incusd daemon by uploading an instance backup tarball whose dependent_volumes[*] block contains a nil snapshot pointer (or omits volume: / pool:). This is a sibling-field variant of the 2026-05-04 batch fix d768f81c0a1d985f35ae56219519822b080bf5e3 ("Properly check dependent volumes on import"). That commit added if disk == nil at the top of the outer loop, but did not guard the four sub-pointer fields the loop body dereferences naked. Version 7.1.0 contains an updated patch.

CVSS v3
2.1
EG Score
2.1LOWmedium confidence
EG Risk
25
EG Risk 25/100

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
Severity21% × 45%
Exploitation40% × 40%
Automatability0% × 15%
EPSS PROB
0.4%
EPSS %ILE
29th
KEV
Not listed

Published

June 26, 2026

Last Modified

September 18, 2026

References (2)

Vendor Advisories for CVE-2026-48754(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(5 across 2 ecosystems)
Go(4)
PackageVulnerable rangeFix by version rangeDependents
github.com/lxc/incus—
  • every version on: no fix on record
—
github.com/lxc/incus/v6—
  • every version on: no fix on record
—
github.com/lxc/incus/v7—
  • every version up to 7.1.0: fixed in 7.1.0
—
github.com/lxc/incus/v7/cmd/incusd—
  • every version up to 7.1.0: fixed in 7.1.0
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
incus6.0.4-2 ... 7.0.0-2~bpo13+1 (24 versions)
  • every version up to 7.0.0-2: fixed in 7.0.0-2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 23× 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-10-06 15:18 UTCEPSS rescore
  2. 2026-10-05 17:43 UTCEPSS rescore
  3. 2026-10-04 23:22 UTCEPSS rescore
  4. 2026-10-03 14:25 UTCEPSS rescore
  5. 2026-10-01 19:50 UTCEPSS rescore
  6. 2026-09-30 15:03 UTCEPSS rescore
  7. 2026-09-28 13:51 UTCEPSS rescore
  8. 2026-09-27 13:48 UTCEPSS rescore
  9. 2026-09-26 15:59 UTCEPSS rescore
  10. 2026-09-26 00:27 UTCEPSS rescore
  11. 2026-09-23 17:53 UTCEPSS rescore
  12. 2026-09-23 07:50 UTCEG score recompute
  13. 2026-09-20 20:16 UTCEPSS rescore
  14. 2026-09-18 20:36 UTCEG score recompute
  15. 2026-09-18 19:28 UTCEPSS rescore
  16. 2026-09-18 07:12 UTCEG score recompute
  17. 2026-09-16 14:08 UTCEPSS rescore
  18. 2026-09-16 05:15 UTCEPSS rescore
  19. 2026-09-13 16:47 UTCEPSS rescore
  20. 2026-09-12 15:34 UTCEG score recompute
  21. 2026-09-11 14:53 UTCEPSS rescore
  22. 2026-09-10 09:35 UTCEPSS rescore
  23. 2026-09-08 22:01 UTCEPSS rescore
  24. 2026-09-06 16:01 UTCEG score recompute
  25. 2026-09-06 13:47 UTCEPSS rescore
Show 22 more
  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-02 14:12 UTCEPSS rescore
  3. 2026-09-01 13:54 UTCEPSS rescore
  4. 2026-09-01 04:40 UTCEPSS rescore
  5. 2026-08-30 19:21 UTCEG score recompute
  6. 2026-08-30 19:17 UTCEPSS rescore
  7. 2026-08-30 01:22 UTCEPSS rescore
  8. 2026-08-28 21:41 UTCEPSS rescore
  9. 2026-08-27 14:25 UTCEPSS rescore
  10. 2026-08-26 18:25 UTCEG score recompute
  11. 2026-08-26 18:11 UTCEG score recompute
  12. 2026-08-26 14:46 UTCEPSS rescore
  13. 2026-08-25 13:49 UTCEPSS rescore
  14. 2026-08-24 12:53 UTCEG score recompute
  15. 2026-08-23 00:19 UTCEPSS rescore
  16. 2026-08-21 15:21 UTCEG score recompute
  17. 2026-08-21 14:54 UTCEG score recompute▲ 2.10
  18. 2026-08-21 14:54 UTCMITRE cvelistV5CVSS v3 → 2.1 · CVSS v4 → 2.1
  19. 2026-08-01 07:29 UTCEG score recompute
  20. 2026-07-26 14:33 UTCEG score recompute
  21. 2026-07-23 03:18 UTCEG score recompute
  22. 2026-06-26 19:37 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-48754?
CVE-2026-48754 is a low vulnerability published on June 26, 2026. Incus is a system container and virtual machine manager. Prior to version 7.1.0, (backend).createDependentVolumesFromBackup in internal/server/storage/backend.go contains a cluster of unguarded pointer derefs on every dependent-volume entry's VolumeSnapshots[i], Volume, and Pool sub-fields. An…
When was CVE-2026-48754 disclosed?
CVE-2026-48754 was first published on June 26, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48754 actively exploited?
CVE-2026-48754 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (29th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48754?
CVE-2026-48754 has a CVSS base score of 2.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-48754?
A fix for CVE-2026-48754 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-48754 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-48754?

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

Book a Demo →Browse All CVEs