CVE-2026-22696

{"id": "CVE-2026-22696", "cveTags": [], "metrics": {"cvssMetricV40": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 9.3, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "valueDensity": "NOT_DEFINED", "vectorString": "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", "exploitMaturity": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "userInteraction": "NONE", "attackComplexity": "LOW", "attackRequirements": "NONE", "privilegesRequired": "NONE", "subIntegrityImpact": "NONE", "vulnIntegrityImpact": "HIGH", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "NONE", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "NONE", "vulnConfidentialityImpact": "HIGH", "confidentialityRequirement": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED"}}]}, "published": "2026-01-26T22:15:55.733", "references": [{"url": "https://github.com/Phala-Network/dcap-qvl/security/advisories/GHSA-796p-j2gh-9m2q", "source": "security-advisories@github.com"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Primary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-295"}, {"lang": "en", "value": "CWE-347"}]}], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "dcap-qvl implementa la l\u00f3gica de verificaci\u00f3n de citas para DCAP (Data Center Attestation Primitives). Una vulnerabilidad presente en versiones anteriores a la 0.3.9 implica una brecha cr\u00edtica en el proceso de verificaci\u00f3n criptogr\u00e1fica dentro de dcap-qvl. La librer\u00eda obtiene el colateral de Identidad QE (incluyendo qe_identity, qe_identity_signature y qe_identity_issuer_chain) del PCCS. Sin embargo, omite verificar la firma de Identidad QE contra su cadena de certificados y no aplica restricciones de pol\u00edtica en el Informe QE. Un atacante puede falsificar los datos de Identidad QE para incluir en la lista blanca un Enclave de Citas malicioso o no Intel. Esto permite al atacante falsificar el QE y firmar citas no confiables que el verificador aceptar\u00e1 como v\u00e1lidas. Efectivamente, esto elude todo el modelo de seguridad de atestaci\u00f3n remota, ya que el verificador ya no puede confiar en la entidad responsable de firmar las citas. Todas las implementaciones que utilizan la librer\u00eda dcap-qvl para la verificaci\u00f3n de citas SGX o TDX est\u00e1n afectadas. La vulnerabilidad ha sido parcheada en la versi\u00f3n 0.3.9 de dcap-qvl. La soluci\u00f3n implementa la verificaci\u00f3n criptogr\u00e1fica faltante para la firma de Identidad QE y aplica las comprobaciones requeridas para MRSIGNER, ISVPRODID e ISVSVN contra el Informe QE. Los usuarios de los paquetes '@phala/dcap-qvl-node' y '@phala/dcap-qvl-web' deber\u00edan cambiar a la implementaci\u00f3n pura de JavaScript, '@phala/dcap-qvl'. No existen soluciones alternativas conocidas para esta vulnerabilidad. Los usuarios deben actualizar a la versi\u00f3n parcheada para asegurar que el colateral de Identidad QE sea verificado correctamente."}], "lastModified": "2026-04-15T00:35:42.020", "sourceIdentifier": "security-advisories@github.com"}