npm package report

Is @phala/dcap-qvl-web safe?

1 known vulnerability, worst severity CRITICAL.

// reach

0 direct dependencies

none carry a known advisory

    0 packages depend on it

    an advisory here reaches each of them

      Create a free accountfor every dependency path, dependent and what to upgrade
      // ai model usage

      Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.

      cvss
      9.3
      critical

      CVSS v4.0 base score out of 10

      epss
      0.21%
      low

      chance of exploitation in 30 days, 10th percentile of all CVEs

      xyz score
      4.0
      medium

      CyberXYZ composite out of 10

      fig. 01 — GHSA-796p-j2gh-9m2q, the advisory selected below

      // 1 advisories

      GHSA-796p-j2gh-9m2q

      CRITICALGitHub ratingCVE-2026-22696
      // 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 @phala/dcap-qvl-node and @phala/dcap-qvl-web packages should switch to the pure JavaScript implementation, @phala/dcap-qvl.

      // 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 <saxenism@bluethroatlabs.com>.

      // cvss v4.0 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
      Network
      Attack complexity
      Low
      Attack requirements
      None
      Privileges required
      None
      User interaction
      None
      Confidentiality (vulnerable system)
      High
      Integrity (vulnerable system)
      High
      Availability (vulnerable system)
      None
      Confidentiality (subsequent systems)
      None
      Integrity (subsequent systems)
      None
      Availability (subsequent systems)
      None

      Checked 2026-10-24 at 20:06 UTC. The most recent advisory here was published 2026-01-26. Updated continuously from NVD, GHSA, OSV and CNA feeds.

      Think a verdict here is wrong? Tell us — we respond within 2 business days.