CVE Intelligence
Analysis AI-assisted

CVE-2026-22696: dcap-qvl Missing QE Identity Signature Verification

dcap-qvl versions before 0.3.9 do not verify the QE Identity signature against its certificate chain and do not enforce policy checks on the QE Report, which can let a forged Quoting Enclave be trusted. The record describes this as a bypass of remote attestation for SGX and TDX quotes, rated critical with a CVSS score of 9.3. The record states the fix is in 0.3.9 and that no workarounds are known.

Published Oct 24, 2026 · Updated Oct 24, 2026 · Ler em português

Overview

dcap-qvl is a library that performs quote verification for DCAP attestation. According to the record, versions before 0.3.9 do not verify the QE Identity signature against its certificate chain and do not enforce policy constraints on the QE Report, which can allow a forged Quoting Enclave identity to be accepted.

Impact

  • The verifier may accept quotes signed by an untrusted or non-Intel Quoting Enclave.
  • The description states this bypasses the remote attestation trust model for SGX and TDX quote verification.
  • The CNA rates the issue critical, with a CVSS score of 9.3.

Affected products and versions

  • Phala-Network Dcap-qvl: before 0.3.9.
  • The description states that all deployments using the library for SGX or TDX quote verification are affected.
  • The packages @phala/dcap-qvl-node and @phala/dcap-qvl-web are named as ones whose users should switch to the pure JavaScript implementation @phala/dcap-qvl.

Exploitation status

The record shows that this CVE is not listed in the CISA KEV catalog, and no confirmed active exploitation appears in the sources consulted. The SSVC data in the record lists exploitation as poc, which is a proof-of-concept indicator and does not confirm exploitation in the wild.

Remediation and mitigation

  • Upgrade dcap-qvl to version 0.3.9, which the description says implements the missing QE Identity signature verification and the MRSIGNER, ISVPRODID and ISVSVN checks against the QE Report.
  • Users of the Node and web packages should move to @phala/dcap-qvl, the pure JavaScript implementation named in the description.
  • The description states there are no known workarounds, so upgrading is the only remediation described.

Detection guidance

  • Inventory where dcap-qvl and the related @phala packages are used, including transitive dependencies, and record the versions in use.
  • Review attestation pipelines to identify which Quoting Enclave identities are trusted and whether those decisions depend on collateral retrieved from the PCCS.
  • Treat unexpected changes in accepted QE identities as events to investigate.

Limitations of the available information

  • The fixes field in the record is empty; the fixed version 0.3.9 comes from the description and the allowed version data.
  • The record does not describe exploitation prerequisites beyond the description, and no attack steps are included here.
  • The record does not show whether any deployed system has already accepted a forged QE identity.
  • Sources consulted: GitHub Security Advisory GHSA-796p-j2gh-9m2q and NVD entry for CVE-2026-22696.

Frequently asked questions

Which versions are affected?

The record lists dcap-qvl versions before 0.3.9 as affected. Version 0.3.9 is the version named in the description as containing the fix.

Is this vulnerability being exploited in the wild?

The record shows no CISA KEV listing for this CVE, and no confirmed active exploitation appears in the sources consulted. The SSVC data only indicates a poc exploitation level.

This analysis was drafted with AI assistance from verified source data and automatically checked against it.