CVE-2026-22696
Cryptographic Verification Bypass in dcap-qvl Enables Quote Forgery
Publication date: 2026-01-26
Last updated on: 2026-01-26
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| phala | dcap-qvl | to 0.3.9 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-347 | The product does not verify, or incorrectly verifies, the cryptographic signature for data. |
| CWE-295 | The product does not validate, or incorrectly validates, a certificate. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the dcap-qvl library versions prior to 0.3.9, which is responsible for verifying quotes in Intel SGX or TDX environments. The issue is that the library fails to verify the QE Identity signature against its certificate chain and does not enforce policy constraints on the QE Report. This allows an attacker to forge QE Identity data to whitelist a malicious or non-Intel Quoting Enclave, enabling them to sign untrusted quotes that the verifier will accept as valid. Essentially, this bypasses the remote attestation security model, making the verifier unable to trust the entity signing the quotes.
How can this vulnerability impact me? :
The vulnerability allows attackers to forge quotes that appear valid to the verifier, effectively bypassing the remote attestation security model. This means that untrusted or malicious enclaves can be accepted as legitimate, potentially leading to unauthorized access, data breaches, or execution of malicious code within trusted environments relying on SGX or TDX quote verification.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you must upgrade the dcap-qvl library to version 0.3.9 or later, which includes the necessary cryptographic verification for the QE Identity signature and enforces policy checks on 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. There are no known workarounds, so upgrading is essential to ensure security.