Incus project isolation bypass in network address sets
- Exploited
- No known exploitation
- Fix
- Fixed in 7.3.0
- Who is exposed
- Not reported
Summary
Incus, a system container and virtual machine manager, lets a client restricted to one project write to network address sets in the default project. An attacker with low-privilege login can exploit this remotely over the network without any user action.
Written by a model
Original description
Incus is a system container and virtual machine manager. Prior to 7.3.0, the six network address set handlers in cmd/incusd/network_address_sets.go resolved the effective project with project.NetworkProject(), which returns default when features.networks is unset. The expandProject authorization switch in cmd/incusd/daemon.go omitted auth.ObjectTypeNetworkAddressSet, so authorization used the requested project instead of the effective project. This issue is fixed in version 7.3.0.
What to do
Upgrade to a fixed version: 7.3.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-81499 (Incus: Project-restricted client can write to the default project's network address sets), 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-81499 (entry last updated 2026-11-19):
Affected:
- lxc incus: fixed in 7.3.0
Fixed versions: 7.3.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-81499 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-81499 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/lxc/incus/security/advisories/GHSA-6v6x-387m-rj4w
- https://github.com/lxc/incus/pull/3750
- https://github.com/lxc/incus/commit/620c836181dd011672541835803f33712aa648fc
- https://github.com/lxc/incus/releases/tag/v7.3.0
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-81499
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-81499"}.Affected versions
- lxc incusfixed in 7.3.0
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.4/10CVSS 5.4
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 6
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · lxc/incus · Advisory GHSA-6v6x-387m-rj4w |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-81499 |
| Record | NVD · CVE-2026-81499 |
| Other links 3 | |
| Repository | GitHub · lxc/incus · Pull request #3750 |
| Repository | GitHub · lxc/incus · Commit 620c8361 |
| Repository | GitHub · lxc/incus · Release v7.3.0 |
Questions about CVE-2026-81499
Is CVE-2026-81499 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
Which versions are affected by CVE-2026-81499?
incus: before 7.3.0.
Source: cve.now feed data
How do I fix CVE-2026-81499?
Upgrade to a fixed version: 7.3.0.
Source: cve.now feed data
Related
- CVE-2026-130778Incus before 7.6.0 Authentication Bypass via Unverified Client Certificate Chains
- CVE-2026-130786Incus before 7.6.0 LXC Configuration Injection via OCI Image Config
- CVE-2026-130784Incus before 7.6.0 Authorization Bypass via Default Project Resource Inheritance
- CVE-2026-130780Incus before 7.6.0 Path Traversal via Dependent Volumes in Migration
- CVE-2026-130773Incus before 7.6.0 Project Isolation Bypass via Default Project Resource Creation
- CVE-2026-115377Incus 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
No corrections so far. Something wrong on this page? Report an error.