Affects dcap-qvl used in SGX/TDX attestation across deployments; bypasses remote attestation by forging QE Identity, enabling code execution and impersonation.
CVE-2026-22696
Remote attestation bypass via forged QE Identity in DCAP-QVL.
Is CVE-2026-22696 being exploited?
Not confirmed. CVE-2026-22696 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.20% probability of exploitation in the next 30 days.
How severe is CVE-2026-22696?
CVE-2026-22696 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-22696?
Yes. A fix has been recorded for CVE-2026-22696. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-22696 affect?
CVE-2026-22696 affects dcap-qvl library (SGX/TDX quote verification), @phala/dcap-qvl-node, @phala/dcap-qvl-web, SGX/TDX attestation deployments. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-22696?
Upgrade to 0.3.9+ or switch to pure JS @phala/dcap-qvl
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Forge QE Identity to sign untrusted quotes; remote attestation trust chain bypassed, enabling remote code execution on SGX/TDX hosts.
Immediate action required
- affected< 0.3.9
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.