Advisory record · GHSA-wj2j-qwcf-cfcc

IncusOS has a LUKS encryption bypass due to insufficient TPM policy

CVSS 7.7 HighEPSS 0.0015 · 3rd percentile

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

PackageEcosystemAffectedFixed in
github.com/lxc/incus-os/incus-osdGo<0.0.0-20260313012803-e3b35f230d230.0.0-20260313012803-e3b35f230d23
Identifiers
GHSA-wj2j-qwcf-cfcc · CVE-2026-32606 · GO-2026-4704
Weakness (CWE)
CWE-522
Published
16 Mar 2026
Updated
26 Mar 2026

Machine-written summary

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

The IncusOS package github.com/lxc/incus-os/incus-osd is affected in versions before 0.0.0-20260313012803-e3b35f230d23, and that version is the fix. An attacker with physical access can swap the encrypted root partition for one they control, have a boot-time unit extract the LUKS volume key from the real disk through the TPM, and then access or modify the original data. Upgrade to 0.0.0-20260313012803-e3b35f230d23 or later; no workarounds are 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
7.7 High 3.1 CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0015, the 3rd percentile, on 12 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.