ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-22696

dcap-qvl has Missing Verification for QE Identity

Published Jan 26, 2026 · catalog updated Oct 27, 2026 · dcap-qvl has Missing Verification

Last checked Oct 29, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-22696. EPSS is 0.21%. Act only if a listed version of dcap-qvl has Missing Verification is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (dcap-qvl has Missing Verification).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Critical—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.21%
Remediation
Advisory link
Affected products
PyPI dcap-qvl · crates.io dcap-qvl · npm @phala/dcap-qvl · npm @phala/dcap-qvl-node · npm @phala/dcap-qvl-web

## 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 cryptographic verification for the QE Identity signature and enforces the required checks for MRSIGNER, ISVPRODID, and ISVSVN against the QE Report. Users of the and packages should switch to the pure JavaScript implementation, . ## Workarounds There are no known workarounds for this vulnerability. Users must upgrade to the patched version to ensure that QE Identity collateral is properly verified. ## Credit This bug was reported by Rahul Saxena .

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • PyPI dcap-qvl0 → 0.3.9
  • crates.io dcap-qvl0 → 0.3.9
  • npm @phala/dcap-qvl0 → 0.3.9
  • npm @phala/dcap-qvl-node0 → 0.3.3
  • npm @phala/dcap-qvl-web0 → 0.3.3

How to fix CVE-2026-22696

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-22696. EPSS is 0.21%. Act only if a listed version of dcap-qvl has Missing Verification is installed.

Which versions are affected?

Compare what you have installed with 0 → 0.3.9, 0 → 0.3.3. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-295: Improper Certificate Validation; CWE-347: Improper Verification of Cryptographic Signature. EPSS 0.21%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Jan 26, 2026 · GitHub Advisory Database

    Detected

    ## 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. ## Cons

  2. Oct 27, 2026 · GitHub Advisory Database

    Fix available

    dcap-qvl fixed in 0.3.9; @phala/dcap-qvl fixed in 0.3.9; dcap-qvl fixed in 0.3.9

  3. Oct 27, 2026 · GitHub Advisory Database

    Fix available

    dcap-qvl fixed in 0.3.9

  4. Oct 27, 2026 · GitHub Advisory Database

    Fix available

    @phala/dcap-qvl fixed in 0.3.9

  5. Oct 27, 2026 · GitHub Advisory Database

    Fix available

    @phala/dcap-qvl-web fixed in 0.3.3

  6. Oct 27, 2026 · GitHub Advisory Database

    Fix available

    @phala/dcap-qvl-node fixed in 0.3.3

  7. Oct 27, 2026 · GitHub Advisory Database

    Updated

    ## 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. ## Cons

Sources

References

Freshness

Last verified in this catalog Oct 28, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • GitHub Advisory DatabaseOct 29, 2026
  • OpenSSF OSV / OSV ScannerOct 29, 2026
  • CVE.orgOct 28, 2026