CVE-2026-32606

HIGHNVD 7.67.6
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.6 from GitHub Security Advisory (severity: HIGH) published 2026-03-16. NVD baseline CVSS 7.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-12779 (ENISA EUVD) · GHSA-wj2j-qwcf-cfcc (GitHub Security Advisories)Source: ENISA EUVD

7.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.6Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

IncusOS is an immutable OS image dedicated to running Incus. Prior to 202603142010, the default configuration of systemd-cryptenroll as used by IncusOS through mkosi allows for an attacker with physical access to the machine to access the encrypted data without requiring any interaction by the system's owner or any tampering of Secure Boot state or kernel (UKI) boot image. That's because in this configuration, the LUKS key is made available by the TPM so long as the system has the expected PCR7 value and the PCR11 policy matches. That default PCR11 policy importantly allows for the TPM to release the key to the booted system rather than just from the initrd part of the signed kernel image (UKI). The attack relies on the attacker being able to substitute the original encrypted root partition for one that they control. By doing so, the system will prompt for a recovery key on boot, which the attacker has defined and can provide, before booting the system using the attacker's root partition rather than the system's original one. The attacker only needs to put a systemd unit starting on system boot within their root partition to have the system run that logic on boot. That unit will then run in an environment where the TPM will allow for the retrieval of the encryption key of the real root disk, allowing the attacker to steal the LUKS volume key (immutable master key) and then use it against the real root disk, altering it or getting data out before putting the disk back the way it was and returning the system without a trace of this attack having happened. This is all possible because the system will have still booted with Secure Boot enabled, will have measured and ran the expected bootloader and kernel image (UKI). The initrd selects the root disk based on GPT partition identifiers making it possible to easily substitute the real root disk for an attacker controlled one. This doesn't lead to any change in the TPM state and therefore allows for retrieval of the LUKS key by the attacker through a boot time systemd unit on their alternative root partition. IncusOS version 202603142010 (2026/03/14 20:10 UTC) includes the new PCR15 logic and will automatically update the TPM policy on boot. Anyone suspecting that their system may have been physically accessed while shut down should perform a full system wipe and reinstallation as only that will rotate the LUKS volume key and prevent subsequent access to the encrypted data should the system have been previously compromised. There are no known workarounds other than updating to a version with corrected logic which will automatically rebind the LUKS keys to the new set of TPM registers and prevent this from being exploited.

CVSS v3
7.6
EG Score
7.6HIGHmedium confidence
EG Risk
50
EG Risk 50/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity76% × 45%
Impact severity (EG Severity): CVSS 7.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.1%
EPSS %ILE
3rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.6): severity, escalated by confirmed exploitation. This CVE's 7.6 is its impact severity (EG Severity), not escalated.

EG Severity
7.6 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

March 18, 2026

Last Modified

June 17, 2026

Advisory Details (5)

Auto-updated Jun 10, 2026
Patch available. Sources: github_commit, github_pr, github.
Web page

Bypassing disk encryption on systems with automatic TPM2 unlock | oddlama's blog

https://oddlama.org/blog/bypassing-disk-encryption-with-tpm2-unlock
GitHub advisoryMentions a patch (unverified)

LUKS encryption bypass due to insufficient TPM policy · Advisory · lxc/incus-os · GitHub

https://github.com/lxc/incus-os/security/advisories/GHSA-wj2j-qwcf-cfcc
GitHub pull request

Adjust LUKS PCR binding policy

Fix merged in lxc/incus-os PR #954 on 2026-03-13 — awaiting tagged release

https://github.com/lxc/incus-os/pull/954
GitHub commit

commit e3b35f230d23 (lxc/incus-os)

Fix landed in lxc/incus-os commit e3b35f230d23 — awaiting tagged release

https://github.com/lxc/incus-os/commit/e3b35f230d23443d27752eac27ebb2b22c957b75
Web page

Potential LUKS encryption bypass through filesystem confusion - IncusOS - Linux Containers Forum

https://discuss.linuxcontainers.org/t/potential-luks-encryption-bypass-through-filesystem-confusion/26348

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/lxc/incus-os/incus-osd @ 0.0.0-20260313012803-e3b35f230d23 (fixes < 0.0.0-20260313012803-e3b35f230d23)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/lxc/incus-os/incus-osd—
  • every version up to 0.0.0-20260313012803-e3b35f230d23: fixed in 0.0.0-20260313012803-e3b35f230d23
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 41× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 218 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 123 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  2. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  3. 2026-11-01 07:54 UTCGHSA enrichmentGHSA-wj2j-qwcf-cfcc · GitHub severity HIGH · GitHub CVSS 7.6
  4. 2026-11-01 07:54 UTCEG score recompute
  5. 2026-11-01 00:43 UTCEG score recompute
  6. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  7. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  8. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  9. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  10. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  11. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  12. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  13. 2026-10-25 14:35 UTCEG score recompute
  14. 2026-10-24 20:16 UTCEG score recompute
  15. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  16. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  17. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  19. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  20. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  21. 2026-10-18 03:47 UTCEG score recompute
  22. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  23. 2026-10-17 15:50 UTCEG score recompute
  24. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  25. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
Show 70 more
  1. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  2. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  3. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  4. 2026-10-12 16:14 UTCEG score recompute
  5. 2026-10-11 19:56 UTCEG score recompute
  6. 2026-10-11 17:09 UTCEG score recompute
  7. 2026-10-11 14:37 UTCEG score recompute
  8. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  9. 2026-10-11 09:44 UTCOSV refresh
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  12. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  13. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  14. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  15. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  16. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  17. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  18. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  19. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  20. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  21. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  22. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  23. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  24. 2026-09-21 22:15 UTCOSV refresh
  25. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  26. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  27. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  28. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  29. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  30. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  31. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  32. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  33. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  34. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  35. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  36. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  37. 2026-09-02 18:08 UTCOSV refresh
  38. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  39. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  40. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  41. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  42. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  43. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  44. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  45. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  46. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  47. 2026-08-24 14:17 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  48. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  49. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  50. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  51. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  52. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  53. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  54. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  55. 2026-08-16 11:18 UTCEG score recompute
  56. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  57. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  58. 2026-08-14 07:26 UTCEG score recompute
  59. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  60. 2026-08-12 22:13 UTCEG score recompute
  61. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  62. 2026-08-11 21:32 UTCEG score recompute
  63. 2026-08-11 04:38 UTCEG score recompute
  64. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  65. 2026-08-09 18:22 UTCEG score recompute
  66. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  67. 2026-08-09 07:00 UTCEG score recompute
  68. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  69. 2026-08-07 17:34 UTCEG score recompute
  70. 2026-08-06 19:30 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-32606?
CVE-2026-32606 is a high-severity vulnerability; its CVE record was published on March 18, 2026. IncusOS is an immutable OS image dedicated to running Incus. Prior to 202603142010, the default configuration of systemd-cryptenroll as used by IncusOS through mkosi allows for an attacker with physical access to the machine to access the encrypted data without requiring any interaction by the…
When was the CVE record for CVE-2026-32606 published?
The CVE record for CVE-2026-32606 was published on March 18, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-32606 actively exploited?
CVE-2026-32606 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-32606?
CVE-2026-32606 has a CVSS v3 base score of 7.6 (NVD).
How do I remediate CVE-2026-32606?
A fix for CVE-2026-32606 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-32606

Explore →

Is Your Infrastructure Affected by CVE-2026-32606?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.