Advisory record · GHSA-796p-j2gh-9m2q

dcap-qvl has Missing Verification for QE Identity

CVSS 9.3 CriticalCriticalEPSS 0.0021 · 10th percentile

Critical, because:

  • CVSS score 9.3: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 26 Jan 2026, 18:55 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
dcap-qvlcrates.io<0.3.90.3.9
@phala/dcap-qvlnpm<0.3.90.3.9
@phala/dcap-qvl-webnpm<=0.3.3No fixed version yet
@phala/dcap-qvl-nodenpm<=0.3.3No fixed version yet
dcap-qvlPyPI<0.3.90.3.9
Identifiers
GHSA-796p-j2gh-9m2q · CVE-2026-22696 · PYSEC-2026-326
Weakness (CWE)
CWE-295 · CWE-347
Published
26 Jan 2026
Updated
27 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The dcap-qvl library, published as crates.io dcap-qvl and PyPI dcap-qvl before 0.3.9 and as npm @phala/dcap-qvl before 0.3.9, does not verify the signature of QE Identity collateral fetched from the PCCS or enforce policy checks on the QE Report. An attacker able to supply forged QE Identity data could whitelist a malicious Quoting Enclave and get untrusted quotes accepted as valid, bypassing remote attestation. Upgrade to 0.3.9. The npm packages @phala/dcap-qvl-node and @phala/dcap-qvl-web have no fixed version listed; the source advises switching to @phala/dcap-qvl.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.3 Critical 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0021, the 10th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 13:33 UTC First seen by agentprime
  2. 31 Oct 2026, 13:33 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.