CVE-2026-32606— IncusOS 安全漏洞
一分钟漏洞结论
影响对象
lxc incus-os
利用判断
存在公开或 AI PoC，应优先验证
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
IncusOS是LXC开源的一个专为容器管理平台设计的不可变操作系统镜像。 IncusOS 202603142010之前版本存在安全漏洞，该漏洞源于默认配置允许物理访问的攻击者通过替换加密根分区来检索LUKS卷密钥，可能导致访问加密数据。
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-32606 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
IncusOS has a LUKS encryption bypass due to insufficient TPM policy
来源: CVE Program / CVE List V5
Vulnerability Description
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.
来源: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
来源: CVE Program / CVE List V5
Vulnerability Type
不充分的凭证保护机制
来源: CVE Program / CVE List V5
Vulnerability Title
IncusOS 安全漏洞
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Description
IncusOS是LXC开源的一个专为容器管理平台设计的不可变操作系统镜像。 IncusOS 202603142010之前版本存在安全漏洞，该漏洞源于默认配置允许物理访问的攻击者通过替换加密根分区来检索LUKS卷密钥，可能导致访问加密数据。
来源: 中国国家信息安全漏洞库 CNNVD
CVSS Information
N/A
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Type
N/A
来源: 中国国家信息安全漏洞库 CNNVD
受影响产品
二、漏洞 CVE-2026-32606 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
Qwen3.6-35B-A3B
· 6155 chars
Pro+ 专属包含：
漏洞复现靶场录像（真实沙箱构建 + 触发，独家）
漏洞原理深度分析
触发条件与影响面
完整可执行 POC 代码
利用链与缓解建议
POC 打包下载
每月 100+ 条 AI 生成额度
三、漏洞 CVE-2026-32606 的情报信息
请登录查看更多情报信息。
CVE-2026-32606 补丁与修复 (2)
CVE-2026-32606 厂商安全公告 (1)
CVE-2026-32606 安全博客文章 (1)
CVE-2026-32606 其他参考 (1)
IV. Related Vulnerabilities
V. Comments for CVE-2026-32606
暂无评论