CVE-2026-53762

{"id": "CVE-2026-53762", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-53762", "role": "CISA Coordinator", "options": [{"exploitation": "poc"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-08-26T17:35:29.165865Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 6.2, "attackVector": "LOCAL", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 3.6, "exploitabilityScore": 2.5}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "veracrypt", "product": "VeraCrypt", "versions": [{"status": "affected", "version": "< 1.26.29"}]}]}], "published": "2026-08-21T19:17:02.570", "references": [{"url": "https://github.com/veracrypt/VeraCrypt/commit/39f93910075e1cf492fcf4a9f99a53c7d0b96b87", "source": "security-advisories@github.com"}, {"url": "https://github.com/veracrypt/VeraCrypt/releases/tag/VeraCrypt_1.26.29", "source": "security-advisories@github.com"}, {"url": "https://github.com/veracrypt/VeraCrypt/security/advisories/GHSA-94c6-mgmv-mqc5", "source": "security-advisories@github.com"}, {"url": "https://github.com/veracrypt/VeraCrypt/security/advisories/GHSA-94c6-mgmv-mqc5", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-916"}]}], "descriptions": [{"lang": "en", "value": "VeraCrypt provides disk encryption with strong security based on TrueCrypt. Prior to 1.26.29, non-default builds created with WOLFCRYPT=1 and WOLFCRYPT_BACKEND route SHA-256 and SHA-512 volume-header key derivation through derive_key_sha256 and derive_key_sha512 in src/Crypto/wolfCrypt.c, where the configured iterations value is discarded and wc_HKDF is used instead of PBKDF2-HMAC. Changing the PIM or iteration count therefore does not increase derivation cost, allowing an attacker with an affected container, disk image, or volume header to perform substantially cheaper offline password guesses. Official precompiled VeraCrypt binaries and normal distribution packages use the standard PBKDF2 backend and are not affected. Volumes created by an affected WOLFCRYPT=1 build require backup and recreation because corrected builds derive different keys. This issue is fixed in version 1.26.29."}, {"lang": "es", "value": "VeraCrypt proporciona cifrado de disco con seguridad robusta basado en TrueCrypt. Antes de la versi\u00f3n 1.26.29, las compilaciones no predeterminadas creadas con WOLFCRYPT=1 y WOLFCRYPT_BACKEND enrutan la derivaci\u00f3n de claves de encabezado de volumen SHA-256 y SHA-512 a trav\u00e9s de derive_key_sha256 y derive_key_sha512 en src/Crypto/wolfCrypt.c, donde el valor de iteraciones configurado se descarta y se utiliza wc_HKDF en lugar de PBKDF2-HMAC. Cambiar el PIM o el recuento de iteraciones, por lo tanto, no aumenta el costo de derivaci\u00f3n, permitiendo a un atacante con un contenedor, imagen de disco o encabezado de volumen afectado realizar suposiciones de contrase\u00f1a sin conexi\u00f3n sustancialmente m\u00e1s baratas. Los binarios precompilados oficiales de VeraCrypt y los paquetes de distribuci\u00f3n normales utilizan el backend PBKDF2 est\u00e1ndar y no se ven afectados. Los vol\u00famenes creados por una compilaci\u00f3n WOLFCRYPT=1 afectada requieren copia de seguridad y recreaci\u00f3n porque las compilaciones corregidas derivan claves diferentes. Este problema est\u00e1 solucionado en la versi\u00f3n 1.26.29."}], "lastModified": "2026-10-14T19:10:00.297", "sourceIdentifier": "security-advisories@github.com"}