# dcap-qvl has Missing Verification for QE Identity Advisory record · `GHSA-796p-j2gh-9m2q` - **Identifiers:** `GHSA-796p-j2gh-9m2q` · `CVE-2026-22696` · `PYSEC-2026-326` - **State:** Confirmed - **Severity:** CVSS 9.3 Critical - **Critical:** Yes: CVSS 9+ - **Weakness (CWE):** [CWE-295](https://cwe.mitre.org/data/definitions/295.html) · [CWE-347](https://cwe.mitre.org/data/definitions/347.html) - **Tags:** [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md) - **Published:** 26 Jan 2026 - **Updated:** 27 Oct 2026 - **Reviewed by a person:** No 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. ## Critical Critical, because: - CVSS score 9.3: 9.0 or more. How we decide what’s critical: ## Affected packages - `dcap-qvl` (crates.io): affected `<0.3.9`; fixed in `0.3.9` - `@phala/dcap-qvl` (npm): affected `<0.3.9`; fixed in `0.3.9` - `@phala/dcap-qvl-web` (npm): affected `<=0.3.3`; no fixed version yet - `@phala/dcap-qvl-node` (npm): affected `<=0.3.3`; no fixed version yet - `dcap-qvl` (PyPI): affected `<0.3.9`; fixed in `0.3.9` ## 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 - 9.3 Critical, CVSS 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`, from 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 - 31 Oct 2026, 13:33 UTC: First seen by agentprime - 31 Oct 2026, 13:33 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-796p-j2gh-9m2q) ## Sources - [GitHub Advisory Database: GHSA-796p-j2gh-9m2q](https://github.com/advisories/GHSA-796p-j2gh-9m2q) - [OSV: GHSA-796p-j2gh-9m2q](https://osv.dev/vulnerability/GHSA-796p-j2gh-9m2q) - - - - - 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. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .