NVD / CVE Program· CNA GitHub_M

CVE-2025-64507: Incus vulnerable to local privilege escalation through custom storage volumes

Noroxi assessment

Priority: Monitor (action score 34/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: incus (Alpine:v3.23) 6.0.6-r0; lxd (Debian:12) 5.0.2-5+deb12u2; incus (Debian:13) 6.0.4-2+deb13u2.

Low priority for now. Upgrade to incus (Alpine:v3.23) 6.0.6-r0; lxd (Debian:12) 5.0.2-5+deb12u2; incus (Debian:13) 6.0.4-2+deb13u2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Incus is a system container and virtual machine manager. An issue in versions prior to 6.0.6 and 6.19.0 affects any Incus user in an environment where an unprivileged user may have root access to a container with an attached custom storage volume that has the `security.shifted` property set to `true` as well as access to the host as an unprivileged user. The most common case for this would be systems using `incus-user` with the less privileged `incus` group to provide unprivileged users with an isolated restricted access to Incus. Such users may be able to create a custom storage volume with the necessary property (depending on kernel and filesystem support) and can then write a setuid binary from within the container which can be executed as an unprivileged user on the host to gain root privileges. A patch for this issue is expected in versions 6.0.6 and 6.19.0. As a workaround, permissions can be manually restricted until a patched version of Incus is deployed.

HighCVSS 8.6 · v4.0—No exploit Fix available

Local privilege escalation

Published: Nov 10, 2025
Updated: Jun 17, 2026
EPSS: 0.1% · 7th percentile
CWE: CWE-269

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 34 / 40 · 8.6 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

CISA SSVC decision

Exploitation: proof of concept
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · GitHub_M: 8.6; NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
linuxcontainers	incus	cpe:2.3:a:linuxcontainers:incus

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

linuxcontainers incusbefore 6.0.6
linuxcontainers incus6.1.0 and later · before 6.19.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

lxc incus
- < 6.0.6, >= 6.1.0, < 6.19.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Alpine:v3.23	incus	from 6.1.0 · before 6.0.6-r0	6.0.6-r0
Debian:12	lxd	from 0	—
Debian:12	lxd	before 5.0.2-5+deb12u2	5.0.2-5+deb12u2
Debian:13	incus	before 6.0.4-2+deb13u2	6.0.4-2+deb13u2
Debian:13	lxd	before 5.0.2+git20231211.1364ae4-9+deb13u2	5.0.2+git20231211.1364ae4-9+deb13u2
Debian:14	incus	before 6.0.5-4	6.0.5-4
Go	github.com/lxc/incus	from 0	—
Go	github.com/lxc/incus/v6	from 6.1.0	—
Go	github.com/lxc/incus/v6	before 6.19.0	6.19.0

Same product

linuxcontainers: all records

Other highest-scoring records for the same primary product.

CVE-2026-33897Incus vulnerable to arbitrary file read and write through pongo templates
39Monitor
CVE-2026-33945Abitrary file write through systemd-creds option
38Monitor
CVE-2026-33898Local Incus UI web server vulnerable to nuthentication bypass
35Monitor

Published before and after this one in the same product

Later →CVE-2026-23953Jan 22, 2026 · Incus container environment configuration newline injection
34Monitor
Later →CVE-2026-23954Jan 22, 2026 · Incus container image templating arbitrary host file read and write
34Monitor
Later →CVE-2026-33542Mar 26, 2026 · Incus does not verify combined fingerprint when downloading images from simplestreams servers
22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
alpine:incus	6.0.6-r0 · Alpine:v3.23	Package registry (OSV)
debian:incus	6.0.4-2+deb13u2 · Debian:13	Package registry (OSV)
debian:lxd	5.0.2+git20231211.1364ae4-9+deb13u2 · Debian:13	Package registry (OSV)
Go:github.com/lxc/incus/v6	6.19.0	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Someone with local access to the system can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability

Attack vector: Local
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: X

Weakness class (CWE)

CWE-269 · Improper Privilege Management

CVSS vector

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/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

nvd-secondary

Root cause

To simplify setup, a service account is granted broad, cluster-wide permissions. The principle of least privilege is skipped during installation.

The bug in code

The whole CWE-269 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

yaml

1kind: ClusterRole
2rules:
3  - apiGroups: ["*"]
4    resources: ["*"]
5    verbs: ["*"]

Fixed

yaml

1kind: Role
2metadata:
3  namespace: lodos-system
4rules:
5  - apiGroups: ["apps"]
6    resources: ["deployments"]
7    verbs: ["get", "list", "update"]

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Abuse Elevation Control MechanismT1548

Change log

Fix✗ → ✓Sep 28, 2026, 10:47 PM UTC

For records you follow, these changes also arrive as notifications. →

All records