CVE Intelligence
Low Memory corruption

CVE-2026-48756 — Incus: CreateCustomVolumeFromBackup nil-pointer dereference on volume_snapshots[*].expires_at (sibling-field variant of GHSA-r7w7)

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.

Published Aug 21, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: GitHub_M

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.4% (30-day exploitation probability)+5

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.38%
ahead of 31% of scored CVEs · Oct 15, 2026
Affects
Lxc
Incus and 1 more
CVSS base
2.1
Low · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Go Github.com/lxc/incus/v7/cmd/incusd: fixed in version 7.1.0 — github.com (GitHub Security Advisories)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Lxc Incus, Go Github.com/lxc/incus/v7/cmd/incusd).
  2. Apply the fixed version or the patch documented under Remediation.
  3. Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Lxc Incus version < 7.1.0 Vulnerable CVE Program (cve.org) e CISA ADP
Go Github.com/lxc/incus/v7/cmd/incusd < 7.1.0 Vulnerable GitHub Security Advisories

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Attack requirements
None
Privileges required
Low
User interaction
None
Scope
X
Confidentiality (vulnerable system)
None
Integrity (vulnerable system)
None
Availability (vulnerable system)
Low
Confidentiality (subsequent)
None
Integrity (subsequent)
None
Availability (subsequent)
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
2.1 CVSS 4.0 Low — — security-advisories@github.com via NIST National Vulnerability Database
2.1 CVSS 4.0 Low — — GitHub_M via CVE Program (cve.org) e CISA ADP
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X (score shown at the top: security-advisories@github.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-476 · NULL Pointer Dereference

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
web/proxy/WAF logsnetwork IDS/IPSendpoint telemetry (EDR)crash dumps

Timeline

What happened to this CVE, newest first.

  • 2026
  • Fix documented
    Oct 15, 2026 · GitHub Security Advisories
  • Affected products added · go/github.com/lxc/incus/v7/cmd/incusd
    Oct 15, 2026 · GitHub Security Advisories
  • Affected products added · lxc/incus
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 15, 2026
  • CVSS changed · 2.1
    Oct 15, 2026 · NIST National Vulnerability Database
  • Source status changed · → Deferred
    Oct 15, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 15, 2026 · Alertas do Telegram
  • CVE published
    Aug 21, 2026 · GitHub_M

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 15, 2026 – Oct 15, 2026
  • 1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

2 on the record

Elsewhere on this site

Lxc
every CVE for this vendor
Memory corruption
same class
CWE-476
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-63125 Incus vulnerable to root RCE via image backup.yaml symlink Aug 21, 2026
  • CVE-2026-62867 Incus has an argument injection in storage volume block.create_options that leads to arbitrary command execution Aug 21, 2026
  • CVE-2026-62940 Incus has a project restriction bypass via instance migration config override Aug 21, 2026
  • CVE-2026-62941 Incus: Cross-project instance copy bypasses target project restrictions via TOCTOU in config merge Aug 21, 2026
  • CVE-2026-63343 Arbitrary File Read/Write: metadata.yaml symlink in image allows host filesystem access as root Aug 21, 2026
  • CVE-2026-62313 Incus: Project restriction `restricted.containers.privilege=isolated` bypassable by omitting `security.idmap.isolated` Aug 21, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-48756 is "Incus: CreateCustomVolumeFromBackup nil-pointer dereference on volume_snapshots[*].expires_at (sibling-field variant of GHSA-r7w7)", rated Low. It affects Incus (Lxc); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 2.1 describes technical severity. EPSS 0.38% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.