dbcve.org
Improper Certificate ValidationWeakness · CWE-295

CVE-2026-22696

CRITICAL · 9.3 CVSS v4.0 Published 2026-01-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The dcap-qvl library used for DCAP quote verification in SGX/TDX remote attestation has a critical flaw where it fetches QE Identity collateral from the PCCS but skips cryptographic verification of the QE Identity signature against its certificate chain and fails to enforce policy constraints (MRSIGNER, ISVPRODID, ISVSVN) on the QE Report. This allows attackers to forge QE Identity data and whitelist a malicious Quoting Enclave, enabling them to sign untrusted quotes that verifiers accept as valid, completely bypassing the remote attestation security model.

MitigationUpgrade dcap-qvl to version 0.3.9 or later to implement the missing QE Identity signature verification and policy enforcement. Applications using @phala/dcap-qvl-node or @phala/dcap-qvl-web should migrate to the pure JavaScript @phala/dcap-qvl package.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify dcap-qvl package installation
    Run 'npm list dcap-qvl' or check package.json for 'dcap-qvl', '@phala/dcap-qvl-node', '@phala/dcap-qvl-web', or '@phala/dcap-qvl' dependencies
    Affected if Any of these packages are present in node_modules or package.json
  2. Determine installed dcap-qvl version
    Run 'npm list dcap-qvl' or check package-lock.json for the installed version number
    Affected if Version is present and is below 0.3.9, or version cannot be determined (older installation)
  3. Check for vulnerable package usage
    Search source code for imports from '@phala/dcap-qvl-node' or '@phala/dcap-qvl-web'
    Affected if Code imports either @phala/dcap-qvl-node or @phala/dcap-qvl-web package
  4. Verify QE Identity verification is implemented
    Review application code or dcap-qvl library configuration to confirm that QE Identity signature verification against certificate chain is performed before quote acceptance
    Affected if No explicit QE Identity signature verification is found in the attestation flow
  5. Confirm policy constraint enforcement on QE Report
    Review code that uses the quote verification function to ensure MRSIGNER, ISVPRODID, and ISVSVN values from the QE Report are validated against expected trusted values
    Affected if Policy constraints on QE Report are not explicitly validated in the verification logic

If dcap-qvl version is below 0.3.9, or if using @phala/dcap-qvl-node/@phala/dcap-qvl-web, or if QE Identity signature verification and policy enforcement are not implemented in the attestation flow, the environment is affected by this CVE.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade dcap-qvl to version 0.3.9 or later to implement the missing QE Identity signature verification and policy enforcement. Applications using @phala/dcap-qvl-node or @phala/dcap-qvl-web should migrate to the pure JavaScript @phala/dcap-qvl package.

Recommended fix High confidence

@phala/dcap-qvl version 0.3.9 or later (or @phala/dcap-qvl-node/@phala/dcap-qvl-web users should migrate to @phala/dcap-qvl)

  1. Identify which dcap-qvl package variant is currently in use (@phala/dcap-qvl-node, @phala/dcap-qvl-web, or @phala/dcap-qvl)
  2. Check the current installed version of the dcap-qvl library in your project
  3. If using @phala/dcap-qvl-node or @phala/dcap-qvl-web, migrate to the pure JavaScript implementation @phala/dcap-qvl
  4. Upgrade the package to version 0.3.9 or later using your package manager (e.g., npm install @phala/dcap-qvl@latest or npm install @phala/dcap-qvl@^0.3.9)
  5. Verify the upgrade was successful by checking the installed version
  6. Test your attestation workflow to ensure the library functions correctly with the patched version
Caveat Users of @phala/dcap-qvl-node and @phala/dcap-qvl-web must migrate to @phala/dcap-qvl - ensure compatibility with your application before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22696 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22696 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data