Skip to main content
Menu
CVEs

CVE

Incus path traversal in custom volume backup snapshot names

Affects Incus versions before 7.6.0, where a user allowed to import custom volumes can craft a backup. Fixed in 7.6.0.

CVE-2026-130779Published Updated Summary written by a model

8.5HighCNA
Exploited
No known exploitation
Fix
Fixed in 7.6.0
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Incus versions before 7.6.0 (affected range is < v7.6.0). The attacker must be a user allowed to import custom volumes.

Summary

Incus before 7.6.0 contains a path traversal vulnerability that allows users permitted to import custom volumes to store unvalidated snapshot names from the backup index configuration section. Attackers can craft a backup with traversal sequences in snapshot names so later deletion removes arbitrary host directories as root, while renaming or mounting operates on arbitrary paths.

Who should check

Teams running Incus before 7.6.0 that let users import custom volume backups, including anyone shipping the incusd Go package (github.com/lxc/incus/v7/cmd/incusd).

“Affected versions < v7.6.0”

github.com

cve.now Index

27Pcve.now Index 27 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach10/20Affects Go packages
  • Severity8.5/10CVSS 8.5
  • No patch0/5No signal

What would change the score

  • Would score about 77 if added to CISA KEV
  • Would score about 72 if CISA's SSVC rates exploitation active
  • Would score about 34 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Incus versions before 7.6.0 (affected range is < v7.6.0). The attacker must be a user allowed to import custom volumes.
  • Upgrade to a fixed version: 7.6.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-130779 (Incus before 7.6.0 Path Traversal via Custom Volume Backup Snapshot Names), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130779 (entry last updated 2026-11-18):
Affected:
- Go package github.com/lxc/incus/v7/cmd/incusd: fixed in 7.6.0
Fixed versions: 7.6.0.
Conditions (all must be true for the bug to be hit):
- Incus versions before 7.6.0 (affected range is < v7.6.0). (source: https://github.com/lxc/incus/security/advisories/GHSA-p45f-gqqj-6qq3)
- The attacker must be a user allowed to import custom volumes. (source: https://github.com/lxc/incus/security/advisories/GHSA-p45f-gqqj-6qq3)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-130779 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130779 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/lxc/incus/security/advisories/GHSA-p45f-gqqj-6qq3
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130779
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130779"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · lxc/incus · Advisory GHSA-p45f-gqqj-6qq3
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-130779
RecordNVD · CVE-2026-130779

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130779

Is CVE-2026-130779 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

A crafted custom volume backup snapshot name can make deleting the volume remove an arbitrary directory on the host as root. Renaming or mounting the volume can also operate on an arbitrary path.Source: github.com

Which versions are affected by CVE-2026-130779?

github.com/lxc/incus/v7/cmd/incusd (Go): before 7.6.0.Source: cve.now feed data

Am I affected, and how do I check?

Incus versions before 7.6.0 are in the affected range, and the setup involves users allowed to import custom volumes. To check, look at the installed Incus version and compare it with 7.6.0.Source: github.com

How do I fix CVE-2026-130779?

Upgrade Incus to 7.6.0 or later, which is the fixed version listed for this vulnerability.Source: github.com

More CVEs