Live › vulnerability › CVE-2026-22696
Go to dashboardThe dcap-qvl library, used to verify SGX and TDX remote attestation quotes, does not verify the signature on QE Identity collateral fetched from the PCCS and does not enforce the QE Report policy checks. An attacker can supply forged QE Identity data to accept a malicious or non-Intel Quoting Enclave and get forged quotes that the verifier treats as valid.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-27 16:25 UTC, 0h before NVD. All times on this page are UTC.
Any deployment that uses dcap-qvl to verify SGX or TDX quotes is affected, because the flaw is in the verifier itself rather than in configuration. Systems that only consume attestation results from a separate, already-patched verifier and never run this library are not directly exposed. Teams should look at attestation verifiers, confidential-computing services and blockchain or TEE backends that embed these packages.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| dcap-qvl | cargo | < 0.3.9 | 0.3.9 |
| @phala/dcap-qvl | npm | <= 0.3.0 | 0.3.9 |
| @phala/dcap-qvl-web | npm | <= 0.3.3 | – |
| @phala/dcap-qvl-node | npm | <= 0.3.3 | – |
| dcap-qvl | pypi | < 0.3.9 | 0.3.9 |
cargo tree -p dcap-qvl or check Cargo.lock for dcap-qvl below 0.3.9npm ls @phala/dcap-qvl @phala/dcap-qvl-node @phala/dcap-qvl-web and check for versions <= 0.3.0 or <= 0.3.3 of the Node and web packagespip show dcap-qvl and check for a version below 0.3.9dcap-qvl to 0.3.9@phala/dcap-qvl to 0.3.9@phala/dcap-qvl-node and @phala/dcap-qvl-web with the pure JavaScript package @phala/dcap-qvl at 0.3.9; no fixed version is listed for the Node and web packagesdcap-qvl to 0.3.9Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
This vulnerability involves a critical gap in the cryptographic verification process within the dcap-qvl.
The library fetches QE Identity collateral (including qe_identity, qe_identity_signature, and qe_identity_issuer_chain) from the PCCS. However, it skips to verify the QE Identity signature against its certificate chain and does not enforce policy constraints on the QE Report.
An attacker can forge the QE Identity data to whitelist a malicious or non-Intel Quoting Enclave. This allows the attacker to forge the QE and sign untrusted quotes that the verifier will accept as valid. Effectively, this bypasses the entire remote attestation security model, as the verifier can no longer trust the entity responsible for signing the quotes.
All deployments utilizing the dcap-qvl library for SGX or TDX quote verification are affected.
The vulnerability has been patched in dcap-qvl version 0.3.9. The fix implements the missing cryptographic verification for the QE Identity signature and enforces the required checks for MRSIGNER, ISVPRODID, and ISVSVN against the QE Report.
Users of the @phala/dcap-qvl-node and @phala/dcap-qvl-web packages should switch to the pure JavaScript implementation, @phala/dcap-qvl.
There are no known workarounds for this vulnerability. Users must upgrade to the patched version to ensure that QE Identity collateral is properly verified.
This bug was reported by Rahul Saxena [email protected].
This page as .md · .json · in your agent: get_signal("CVE-2026-22696")
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.