CVE-2026-32606 — exploitation intelligence Public proof-of-concept exploit is available. EPSS exploitation probability: 0.1%. Severity: HIGH.
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.
Create a free account to see public exploit repositories, affected software and versions, references, and the SSVC patch decision for your environment.
Harpia — live CVE exploitation intelligence.
Exploitation intelligence
See what attackers are using now. Harpia continuously correlates exploit maturity, active exploitation, threat activity, and vulnerability context so security teams can prioritize remediation with evidence, not severity alone.
Sign in to search · No credit card · Machine-readable intelligence
HARPIA / LIVE LOOKUP
CVE, component, or advisory ID Check
Is it exploited in the wild?
try CVE-2024-3400 log4j product:openssl version:<3.0 exploited:true
Advanced search syntax Search syntax
CVE & advisory IDs
CVE-2021-44228 GHSA-jfh8-c2jp-5v3q RHSA-2025:1746 DSA-5020-1 Full text
heap OR buffer overflow microsoft -windows "use after free" Scores & evidence
cvss:>=9 exploits:>5 risk:>1.5 Threat flags
exploited:true ransomware:true maturity:weaponized trending:true has: shorthands
has:exploit has:poc has:fix has:repo Software
vendor:microsoft product:log4j ecosystem:npm fixable:true product:openssl version:3.0 Weakness & combinations
cwe:injection cwe:rce exploited:true age:<365 vendor:microsoft trending:true Who & why Pro
Origin and target accept ISO-2, a country name, or a partial word.
actor:qilin origin:RU motivation:espionage sector:healthcare target:AE target:"united arab emirates" ATT&CK, CAPEC & tactics Pro
ttp:T1190 ttp:"public-facing" tactic:"credential access" tactic:TA0010 capec:CAPEC-233 Worked examples Pro
Exploited healthcare exposure with a fixsector:healthcare exploited:true has:fix GCC-targeted and exploited in the wild(target:"united arab emirates" OR target:"saudi arabia" OR target:qatar OR target:kuwait OR target:bahrain OR target:oman) exploited:true UAE-targeted, exploited, fix availabletarget:"united arab emirates" exploited:true has:fix Fresh in-the-wild initial-access activitytactic:"initial access" exploited:true age:<365 CN- or RU-origin activity affecting Microsoft products(origin:CN OR origin:RU) vendor:microsoft exploited:true Espionage-motivated government targeting with no fixmotivation:espionage sector:government NOT has:fix Perimeter-exploitation techniques in npm, fixablettp:T1190 ecosystem:npm fixable:true AND is implicit · OR / NOT / - / parentheses supported · quote a phrase to match it literally · click any example to run it
37.7% of exploited CVEs attacked before disclosure
60.7% under attack within 24 hours
93% of what CVSS calls Critical has no weaponized exploit
15 days ahead of CISA KEV
Threat pulse
Trending in the vulnerability ecosystem. Movement matters. Harpia tracks rising exploit activity, public repositories, exploitation evidence and observed probing to surface what deserves attention next.
Loading live feed signals…
Built into Harpia
Track activity, not just scores. The feed supports trending and momentum views for teams that need a short daily list of what is accelerating.
GET /api/v1/vulnerabilities/searchView global and location trends Prioritize with evidence
Severity is context. Exploitation is intent. Harpia separates theoretical impact from operational urgency, helping teams concentrate remediation capacity where attacker behavior changes the decision.
How Harpia decides 01 Disclosed A vulnerability exists. Severity describes potential impact.
02 PoC / weaponized Exploit code changes feasibility and attacker cost.
03 Exploited in the wild Real-world evidence changes remediation urgency.
04 Decision Immediate · Out of cycle · Scheduled · Defer.
Developer first
One feed. Every security workflow. Search interactively or operationalize the same intelligence in pipelines, SIEM enrichment, TIPs, patch queues, and security products.
From one lookup to continuous enrichment. The web experience and machine interfaces resolve against the same exploitation evidence and decision context.
Open developer documentation GET /api/v1/vulnerabilities/CVE-2024-3400
{
"x_intel_priority": {
"exploited_in_wild": true,
"exploit_maturity": "active",
"cisa_kev": true
}
}REST API STIX 2.1 TAXII 2.1 Bulk API Delta sync SIEM / SOAR
Start with evidence Prioritize what attackers are exploiting now. See whether attackers are already using the vulnerability.
Checking the feed… Loading the advisory record.
