All vulnerabilities
CVE-2026-22696GHSA-796p-j2gh-9m2qPYSEC-2026-326

dcap-qvl has Missing Verification for QE Identity

Phala-Network dcap-qvlrustLibraries & packages
Open in ThreatlineRecord JSON
CVSS
9.3Critical
ExploitationPublic exploit codeCISA's assessment says proof of concept code is public, assessed 27 Jan 2026. Not in the KEV catalogCISA via CVE List
Exploit odds (EPSS)0.21%Chance of exploitation activity in the next 30 days, higher than 10% of CVEs. Scored 27 Oct 2026FIRST EPSS
Fixed in0.3.9Fixed versionGitHub
Published26 Jan 2026Updated 27 Oct 2026CVE List

What fixes it

  • 0.3.9dcap-qvl, rustGitHub
  • 0.3.9@phala/dcap-qvl, npmGitHubnpm install @phala/dcap-qvl@0.3.9
  • 0.3.9dcap-qvl, crates.ioOSVcargo update -p dcap-qvl --precise 0.3.9

A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.

Description

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 <saxenism@bluethroatlabs.com>.

Text from GitHub Advisory Database

Affected versions 23

  • dcap-qvl, rust< 0.3.9GitHub
  • @phala/dcap-qvl, npm<= 0.3.0GitHub
  • @phala/dcap-qvl-web, npm<= 0.3.3GitHub
  • @phala/dcap-qvl-node, npm<= 0.3.3GitHub
  • dcap-qvl, pip< 0.3.9GitHub
  • dcap-qvlaffected: < 0.3.9CVE List
  • dcap-qvl, crates.iofrom first release, fixed in 0.3.9OSV
  • @phala/dcap-qvl, npmfrom first release, fixed in 0.3.9OSV
  • @phala/dcap-qvl-web, npmfrom first release, through 0.3.3OSV
  • @phala/dcap-qvl-node, npmfrom first release, through 0.3.3OSV
  • dcap-qvl, PyPIfrom first release, fixed in 0.3.9OSV
  • dcap-qvl, PyPI0.1.0OSV
  • dcap-qvl, PyPI0.1.1OSV
  • dcap-qvl, PyPI0.1.2OSV
  • dcap-qvl, PyPI0.1.3OSV
  • dcap-qvl, PyPI0.2.2OSV
  • dcap-qvl, PyPI0.3.0OSV
  • dcap-qvl, PyPI0.3.2OSV
  • dcap-qvl, PyPI0.3.4OSV
  • dcap-qvl, PyPI0.3.5OSV
  • dcap-qvl, PyPI0.3.6OSV
  • dcap-qvl, PyPI0.3.7OSV
  • dcap-qvl, PyPI0.3.8OSV

References 5