critical · 9.3 Partly patched

dcap-qvl has Missing Verification for QE Identity

CVE-2026-22696 · GHSA-796p-j2gh-9m2q · PYSEC-2026-326 · published 26 Jan 2026

How serious is it

  • Severity: critical, CVSS score 9.3 out of 10.
  • No exploit prediction (EPSS) score yet.
  • Not on the CISA list of exploited vulnerabilities.
  • No public exploit in Exploit-DB.

Is your app affected by CVE-2026-22696?

Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.

Who is affected

  • dcap-qvl (crates.io) < 0.3.9
  • @phala/dcap-qvl (npm) <= 0.3.0
  • @phala/dcap-qvl-web (npm) <= 0.3.3
  • @phala/dcap-qvl-node (npm) <= 0.3.3
  • dcap-qvl (PyPI) < 0.3.9

How to check

  1. Run cargo tree -i dcap-qvl in your project to see the installed version, including copies pulled in by other packages.
  2. Run npm ls @phala/dcap-qvl in your project to see the installed version, including copies pulled in by other packages.
  3. Run npm ls @phala/dcap-qvl-web in your project to see the installed version, including copies pulled in by other packages.
  4. Run npm ls @phala/dcap-qvl-node in your project to see the installed version, including copies pulled in by other packages.
  5. Run pip show dcap-qvl in your project to see the installed version, including copies pulled in by other packages.
  6. Or paste your lockfile into the checker: it lists every package with a known vulnerability, this one included.
  7. Or run npx shippable-dev scan localhost:3000 in your project folder. It reads your lockfile and flags this vulnerability along with every other known one.

How to fix

Copies a prompt for Claude Code, Cursor or Codex: it checks your lockfiles for this and upgrades it.
  1. On < 0.3.9: Upgrade dcap-qvl to 0.3.9 or later, commit the lockfile and redeploy.
  2. On <= 0.3.0: Upgrade @phala/dcap-qvl to 0.3.9 or later, commit the lockfile and redeploy.
  3. No fixed version of @phala/dcap-qvl-web yet. Replace or remove it, or apply the workaround in the advisory below.
  4. No fixed version of @phala/dcap-qvl-node yet. Replace or remove it, or apply the workaround in the advisory below.
  5. On < 0.3.9: Upgrade dcap-qvl to 0.3.9 or later, commit the lockfile and redeploy.
  6. If a vulnerable version was live, check your logs and rotate the secrets that server could read.

The advisory

## 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>.

Check your whole app

Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.

References

Merged from GitHub Advisory Database, OSV. Last updated 28 Oct 2026. All vulnerabilities · RSS · JSON

Get alerts for new exploited vulnerabilities