CVE-2026-48756

LOWPre-NVD 2.12.1
EchelonGraph scoreLOW confidence

This low-severity CVE scores 2.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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: secondary
Trending — 3 sources updated this week
2.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 2.1Exploit: None knownExposed: 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.1.0, (*backend).CreateCustomVolumeFromBackup in internal/server/storage/backend.go contains an unguarded *time.Time dereference on the ExpiresAt field of every volume-snapshot entry in an imported custom-volume backup. An authenticated user with can_create_storage_volumes permission on any project can crash the incusd daemon by uploading a backup tarball whose volume_snapshots[*].expires_at field is absent. This is a sibling-field variant of GHSA-r7w7-mmxr-47r9 (CVE-2026-40197). Commit 985a1dedf9f3e7ba729c93b654905ed510de25c2 added if s == nil at the top of the loop body, but did not guard the adjacent *snapshot.ExpiresAt deref 19 lines later. Every other consumer of Config.VolumeSnapshots[i].ExpiresAt in this same file already gates the deref with a nil-check — the asymmetric guard is the bug. Version 7.1.0 contains an updated patch.

CVSS v3
2.1
EG Score
2.1(low)
EG Risk
9(Track)
EG Risk 9/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
Severity21% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
14%
KEV
Not listed

Published

June 26, 2026

Last Modified

August 21, 2026

References (1)

Vendor Advisories for CVE-2026-48756(1)

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

Affected Packages

(6 across 3 ecosystems)
Go(4)
PackageVulnerable rangeFixed inDependents
github.com/lxc/incus———
github.com/lxc/incus/v6———
github.com/lxc/incus/v7—7.1.0—
github.com/lxc/incus/v7/cmd/incusd—7.1.0—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
incus6.0.4-2 ... 6.0.4-2+deb13u7~bpo12+1 (15 versions)6.0.4-2+deb13u8—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
incus6.0.4-2 ... 7.0.0-2~bpo13+1 (24 versions)7.0.0-2—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 8× 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:19 UTCEPSS rescore
  2. 2026-08-21 22:27 UTCEG score recompute
  3. 2026-08-21 21:54 UTCEG score recompute
  4. 2026-08-21 15:21 UTCEG score recompute
  5. 2026-08-21 14:24 UTCEG score recompute▲ 2.10
  6. 2026-08-21 14:24 UTCMITRE cvelistV5CVSS v3 → 2.1 · CVSS v4 → 2.1
  7. 2026-08-01 11:24 UTCEG score recompute
  8. 2026-07-26 14:33 UTCEG score recompute
  9. 2026-07-23 03:18 UTCEG score recompute
  10. 2026-06-26 19:37 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-48756?
CVE-2026-48756 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).CreateCustomVolumeFromBackup in internal/server/storage/backend.go contains an unguarded time.Time dereference on the ExpiresAt field of every volume-snapshot entry in an imported custom-volume backup. An…
When was CVE-2026-48756 disclosed?
CVE-2026-48756 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-48756 actively exploited?
CVE-2026-48756 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 86.4% of all scored CVEs.
What is the CVSS score of CVE-2026-48756?
CVE-2026-48756 has a CVSS v3 base score of 2.1 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-48756?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48756, 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-48756

Explore →

Is Your Infrastructure Affected by CVE-2026-48756?

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

Start Free Scan →Browse All CVEs