Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
Check your stack
CVE-2026-115377critical9.9

Incus before 6.0.7, 6.1.0 before 7.0.2, and 7.1.0 before 7.5.0 Arbitrary File Write via Symlink in Migration Stream

Impact

Incus versions before 6.0.7, 6.1.0 before 7.0.2, and 7.1.0 before 7.5.0 have an arbitrary file write vulnerability via symlinks in migration streams. Attackers can craft malicious streams to write host files. This may allow full host compromise.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Affected packages

This source has no supported package-version data for matching. You can read the advisory here, but this record alone cannot power a dependency check.

Affected products

Vendor version evidence. Product records are separate from automatic dependency matching.

lxc · VulnCheck

incus

6 ranges

Package identity

pkg:golang/github.com/lxc/incus/v7/cmd/incusdExplore github.com/lxc/incus/v7/cmd/incusd →

Identity supplied by VulnCheck. Version matching requires compatible range evidence.

Compare with this publisher’s ranges. This does not inspect your installation.

affected

0 → before 6.0.7

semver versions

6.1.0 → before 7.0.2

semver versions

7.1.0 → before 7.5.0

semver versions

unaffected

6.0.7

semver versions

7.0.2

semver versions

7.5.0

semver versions

unknown

Other versions: unaffected

Original source description

Incus before 6.0.7, 6.1.0 before 7.0.2, and 7.1.0 before 7.5.0 contains an arbitrary file write vulnerability that allows malicious migration sources to write host files by planting symlinks in transferred volumes. Attackers can craft rsync or btrfs receive streams with a symlink such as rootfs pointing to the host root, writing files as root for full host compromise.

Inside the record

Evidence available

Package identity
Version evidence
Remediation guidance · not supplied
Weakness classification
Additional publishers

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-115377

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-59 ↗

Improper Link Resolution Before File Access ('Link Following')

VulnCheck

Related →

Environment requirements

These conditions apply together as specified by the publisher. A matching product name alone does not establish exposure.

VulnCheck · platform conditions

Any condition may hold

Vulnerable product

cpe:2.3:a:linuxcontainers:incus:*:*:*:*:*:*:*:*

Before: 6.0.7

Vulnerable product

cpe:2.3:a:linuxcontainers:incus:*:*:*:*:*:*:*:*

From (inclusive): 6.1.0

Before: 7.0.2

Vulnerable product

cpe:2.3:a:linuxcontainers:incus:*:*:*:*:*:*:*:*

From (inclusive): 7.1.0

Before: 7.5.0

Original applicability statements
[
  {
    "nodes": [
      {
        "operator": "OR",
        "negate": false,
        "cpeMatch": [
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:a:linuxcontainers:incus:*:*:*:*:*:*:*:*",
            "versionEndExcluding": "6.0.7"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:a:linuxcontainers:incus:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "6.1.0",
            "versionEndExcluding": "7.0.2"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:a:linuxcontainers:incus:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "7.1.0",
            "versionEndExcluding": "7.5.0"
          }
        ]
      }
    ]
  }
]
Contributing organizations · 2
VulnCheck

Assigning organization

2026-10-22
CISA-ADP

Additional data publisher

2026-10-29

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.

References

2 sources