dcap-qvl has Missing Verification for QE Identity

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

9.3 · 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 · score source

EPSS

• CVE-2026-22696: 0.21% estimated exploitation activity in the next 30 days; percentile 10.49 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

26 Jan 2026, 18:55 UTC

Last modified by the source

27 Oct 2026, 16:30 UTC

Source last checked

28 Oct 2026, 06:00 UTC

1. Revision 6 · amended · 28 Oct 2026

   Amended from osv record GHSA-796p-j2gh-9m2q

2. Revision 5 · amended · 27 Oct 2026

   Amended from ghsa record GHSA-796p-j2gh-9m2q

3. Revision 4 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-796p-j2gh-9m2q

4. Revision 3 · amended · 24 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

5. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-796p-j2gh-9m2q

6. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-796p-j2gh-9m2q

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-22696

Advisory: dcap-qvl has Missing Verification for QE Identity
IDs: CVE-2026-22696, GHSA-796p-j2gh-9m2q
Record: https://patchnext.com/advisories/cve-2026-22696 (revision 6, source checked 28 Oct 2026, 06:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: dcap-qvl 0.3.9; @phala/dcap-qvl 0.3.9; dcap-qvl 0.3.9. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io dcap-qvl: affected < 0.3.9; fixed in 0.3.9
- npm @phala/dcap-qvl-node: affected <= 0.3.3
- npm @phala/dcap-qvl: affected < 0.3.9; fixed in 0.3.9
- PyPI dcap-qvl: affected < 0.3.9; fixed in 0.3.9
- npm @phala/dcap-qvl-web: affected <= 0.3.3

## Suggested inspection (read-only)
- crates.io dcap-qvl: check the installed version with your package manager.
- `npm ls @phala/dcap-qvl-node --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @phala/dcap-qvl --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `python -m pip show dcap-qvl`: prints the installed version. Run with the environment that serves production active.
- `npm ls @phala/dcap-qvl-web --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on dcap-qvl, @phala/dcap-qvl-node, @phala/dcap-qvl, @phala/dcap-qvl-web.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-796p-j2gh-9m2q (GitHub-reviewed advisory GHSA-796p-j2gh-9m2q lists affected ranges: npm @phala/dcap-qvl >=0 =0 =0 =0 <0.3.9)
- Verified: https://osv.dev/vulnerability/GHSA-796p-j2gh-9m2q (OSV record GHSA-796p-j2gh-9m2q lists affected ranges: crates.io dcap-qvl >=0 =0 =0 =0 =0 <0.3.9 (fixed))
- Verified: https://github.com/advisories/GHSA-796p-j2gh-9m2q (GitHub-reviewed advisory GHSA-796p-j2gh-9m2q lists affected ranges: crates.io dcap-qvl >=0 =0 =0 =0 =0 <0.3.9)

Commands are suggestions: review each one before running it.