Answer in brief
CVE-2026-22696 records a Critical severity (CVSS 0.0) vulnerability in dcap-qvl has Missing Verification for QE Identity. The current sources do not mark it as known exploited. The current feed maps dcap-qvl (crates.io), @phala/dcap-qvl (npm), @phala/dcap-qvl (npm), @phala/dcap-qvl (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 0.0. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps dcap-qvl (crates.io), @phala/dcap-qvl (npm), @phala/dcap-qvl (npm), @phala/dcap-qvl (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| dcap-qvlcrates.io | >=0 <0.3.9 | 0.3.9 |
| @phala/dcap-qvlnpm | <=0.3.0 | 0.3.9 |
| @phala/dcap-qvlnpm | <=0.3.0 | 0.3.9 |
| @phala/dcap-qvlnpm | >=0 <0.3.9 | 0.3.9 |
| @phala/dcap-qvl-nodenpm | <=0.3.3 | Not reported |
| @phala/dcap-qvl-nodenpm | <=0.3.3 | Not reported |
| @phala/dcap-qvl-nodenpm | >=0 | Not reported |
| @phala/dcap-qvl-webnpm | <=0.3.3 | Not reported |
| @phala/dcap-qvl-webnpm | <=0.3.3 | Not reported |
| @phala/dcap-qvl-webnpm | >=0 | Not reported |
| dcap-qvlpip | <0.3.9 | 0.3.9 |
| dcap-qvlpypi | >=0 <0.3.9 | 0.3.9 |
| dcap-qvlrust | <0.3.9 | 0.3.9 |
Published upstream
Jan 26, 2026
Evidence: source:ghsa:source_dates:source-dates:recordSource modified
Oct 27, 2026
Evidence: source:ghsa:source_dates:source-dates:recordFirst seen by HOL
Oct 27, 2026
## Impact 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. ## Consequences 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. ## Who is impacted All deployments utilizing the dcap-qvl library for SGX or TDX quote verification are affected. ## Patches 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`. ## Workarounds There are no known workarounds for this vulnerability. Users must upgrade to the patched version to ensure that QE Identity collateral is properly verified. ## Credit This bug was reported by Rahul Saxena <[email protected]>.
Quoted source text, attributed separately from HOL analysis.