Advisory record · GHSA-q4q8-7f2j-9h9f

Incus has an abitrary file write through its systemd-creds options

CVSS 10.0 CriticalCriticalEPSS 0.0046 · 40th percentile

Critical, because:

  • CVSS score 10.0: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 27 Mar 2026, 17:22 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/lxc/incus/v6Go<6.23.06.23.0
Identifiers
GHSA-q4q8-7f2j-9h9f · CVE-2026-33945 · GO-2026-4884
Weakness (CWE)
CWE-22
Published
27 Mar 2026
Updated
7 Apr 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Incus versions before 6.23.0 are vulnerable. An attacker who can set instance configuration keys can use a crafted systemd credential name to write arbitrary files on the host as root, which may allow privilege escalation or denial of service. Upgrade to Incus 6.23.0 or later. No workaround is listed.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
10.0 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0046, the 40th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:08 UTC First seen by agentprime
  2. 31 Oct 2026, 15:08 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.