LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22696: dcap-qvl has Missing Verification for QE Identity

dcap-qvl implements the quote verification logic for DCAP (Data Center Attestation Primitives). A vulnerability present in versions prior to 0.3.9 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. 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. All deployments utilizing the dcap-qvl library for SGX or TDX quote verification are affected. 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`. There are no known workarounds for this vulnerability. Users must upgrade to the patched version to ensure that QE Identity collateral is properly verified.

CriticalCVSS 9.3Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-22696 breaks the trust decision in Phala Network’s dcap-qvl quote verification. A verifier may accept forged attestation data as valid, undermining SGX or TDX remote attestation. Organizations using affected dcap-qvl versions should treat this as urgent because attestation results may no longer prove the expected trusted enclave identity.

Executive priority

Prioritize immediate remediation for any environment relying on SGX or TDX attestation decisions. This vulnerability can invalidate a core trust control, so affected services should be upgraded before relying on attestation outcomes for sensitive workloads, access decisions, or customer assurances.

Technical view

dcap-qvl versions before 0.3.9 fetch QE Identity collateral from PCCS but fail to verify the QE Identity signature against its certificate chain and fail to enforce MRSIGNER, ISVPRODID, and ISVSVN policy checks against the QE Report. This can allow forged QE Identity data to whitelist an untrusted Quoting Enclave and validate untrusted quotes.

Likely exposure

Exposure is limited to deployments using Phala Network dcap-qvl before 0.3.9 for SGX or TDX quote verification, including dependent use through affected node or web packages. Systems not using dcap-qvl for quote verification are not indicated as affected by the provided sources.

Exploitation context

The CVSS vector indicates network attackability, low complexity, no privileges, and no user interaction. The provided sources do not report active exploitation, and the CVE is not marked in KEV. Impact is severe because successful abuse defeats the remote attestation trust model rather than only causing a local failure.

Researcher notes

Key weakness classes are CWE-295 and CWE-347. The issue is missing cryptographic validation of QE Identity collateral and missing policy enforcement on QE Report fields. The advisory states the fix adds signature-chain verification plus MRSIGNER, ISVPRODID, and ISVSVN checks. Evidence does not include exploit-in-the-wild reporting.

Mitigation direction

  • Upgrade dcap-qvl to version 0.3.9 or later.
  • For @phala/dcap-qvl-node, switch to @phala/dcap-qvl.
  • For @phala/dcap-qvl-web, switch to @phala/dcap-qvl.
  • Do not rely on workarounds; none are identified in the sources.
  • Review vendor advisory for deployment-specific guidance.

Validation and detection

  • Inventory applications performing SGX or TDX quote verification.
  • Identify direct and transitive dcap-qvl package versions.
  • Confirm deployed dcap-qvl is 0.3.9 or later.
  • Check for @phala/dcap-qvl-node or @phala/dcap-qvl-web usage.
  • Verify attestation services were rebuilt and redeployed after upgrade.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-295: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-347: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-22696 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.3 (4.0)
Known Exploited
No
Published

Vector: 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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.3CVSS 4.0CriticalCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

9.3Critical
CVSS 4.0 vector shape for CVE-2026-22696Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: 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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Phala-Networkdcap-qvl< 0.3.9Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-295 · source CWE mapping

Improper Certificate Validation

Improper Certificate Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-347 · source CWE mapping

Improper Verification of Cryptographic Signature

Improper Verification of Cryptographic Signature represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.