Attestation bypass via unsigned QE Identity collateral
Published Jan 26, 2026 · Updated Jan 26, 2026
Cryptographic verification failure in Phala dcap-qvl before 0.3.9 allows remote attackers to make forged SGX or TDX quotes appear valid. The verifier accepts QE Identity collateral from PCCS without validating its signature chain or matching MRSIGNER, ISVPRODID, and ISVSVN to the QE Report. Exploitation requires a deployment to verify attacker-controlled collateral and quotes, allowing a malicious or non-Intel Quoting Enclave to impersonate trusted hardware.
Summary
What happened
Cryptographic verification failure in Phala dcap-qvl before 0.3.9 allows remote attackers to make forged SGX or TDX quotes appear valid. The verifier accepts QE Identity collateral from PCCS without validating its signature chain or matching MRSIGNER, ISVPRODID, and ISVSVN to the QE Report. Exploitation requires a deployment to verify attacker-controlled collateral and quotes, allowing a malicious or non-Intel Quoting Enclave to impersonate trusted hardware.
The record
- CVE
- CVE-2026-22696
- Published
- Jan 26, 2026
- Updated
- Jan 26, 2026
- Vendor
- Phala
- Product
- dcap-qvl
- Classifications
- CWE-295, CWE-347, T1553
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 26, 2026CVE publishedPublication date reported by the CVE source.
- Jan 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.3.9
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo