CVE-2026-73567

{"id": "CVE-2026-73567", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-73567", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "yes"}, {"technicalImpact": "total"}], "version": "2.0.3", "timestamp": "2026-08-14T17:55:19.387144Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 9.1, "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 5.2, "exploitabilityScore": 3.9}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "JuneAndGreen", "product": "sm-crypto", "versions": [{"status": "affected", "version": "< 0.5.0"}]}]}], "published": "2026-08-13T18:18:19.387", "references": [{"url": "https://github.com/JuneAndGreen/sm-crypto/commit/1f9bd7bd160c24efd9c26c8f7fda997c68c823d0", "source": "security-advisories@github.com"}, {"url": "https://github.com/JuneAndGreen/sm-crypto/security/advisories/GHSA-vh45-f885-3848", "source": "security-advisories@github.com"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-338"}]}], "descriptions": [{"lang": "en", "value": "sm-crypto provides JavaScript implementations of the Chinese cryptographic algorithms SM2, SM3, and SM4. Prior to 0.5.0, the default no-argument sm2.generateKeyPairHex() path in Node.js uses the module-wide SecureRandom instance in src/sm2/utils.js, supplied by jsbn@1.1.0, which seeds an ARC4 stream from Math.random() and new Date().getTime() because window.crypto.getRandomValues is unavailable even though globalThis.crypto exists. An attacker who can observe the process's Math.random() outputs and estimate the key-generation time can reconstruct the seed, recover generated SM2 private keys, and predict signing ephemeral scalars used to forge signatures. This issue is fixed in version 0.5.0."}, {"lang": "es", "value": "sm-crypto proporciona implementaciones de JavaScript de los algoritmos criptogr\u00e1ficos chinos SM2, SM3 y SM4. Antes de la versi\u00f3n 0.5.0, la ruta predeterminada sin argumentos de sm2.generateKeyPairHex() en Node.js utiliza la instancia SecureRandom de \u00e1mbito de m\u00f3dulo en src/sm2/utils.js, proporcionada por jsbn@1.1.0, que inicializa un flujo ARC4 a partir de Math.random() y new Date().getTime() porque window.crypto.getRandomValues no est\u00e1 disponible aunque globalThis.crypto exista. Un atacante que puede observar las salidas de Math.random() del proceso y estimar el tiempo de generaci\u00f3n de claves puede reconstruir la semilla, recuperar las claves privadas SM2 generadas y predecir los escalares ef\u00edmeros de firma utilizados para falsificar firmas. Este problema est\u00e1 solucionado en la versi\u00f3n 0.5.0."}], "lastModified": "2026-10-24T15:10:00.190", "sourceIdentifier": "security-advisories@github.com"}