{"answers":{"affected":"2 open source packages ship an affected version, including sm-crypto.","exploited":"There is no known exploitation of CVE-2026-73567 in the wild and no public exploit code.","fix":"Upgrade sm-crypto to 0.5.0 or later.","what":"CVE-2026-73567 is a critical vulnerability in JuneAndGreen sm-crypto, published on 13 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-73567 and fix it if it is affected.\n\nWhat it is: CVE-2026-73567 is a critical vulnerability in JuneAndGreen sm-crypto, published on 13 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-73567 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- sm-crypto (npm): affected all versions; fixed in 0.5.0\n- sm-crypto (npm): affected all versions; fixed in 0.5.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-73567/ (Markdown: https://insights.sbomify.com/CVE-2026-73567/index.md)","id":"CVE-2026-73567","markdown":"https://insights.sbomify.com/CVE-2026-73567/index.md","name":"CVE-2026-73567","record":{"aliases":["GHSA-vh45-f885-3848"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript crypto library","requires_auth":"none","summary":"Attackers can recover SM2 private keys and forge signatures due to predictable random number generation in the sm-crypto library.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-338","name":"Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)"}],"description":"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"sm-crypto: Predictable SM2 key generation in Node.js: default RNG uses Math.random + wall clock","id":"CVE-2026-73567","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"weak_cryptography","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"py-libp2p: yamux connection DoS via oversized data frame","id":"CVE-2026-73568"},"packages":[{"ecosystem":"npm","fixed":["0.5.0"],"introduced":["0"],"last_affected":[],"package":"sm-crypto","purl":null,"source":"GHSA-vh45-f885-3848"},{"ecosystem":"npm","fixed":["0.5.0"],"introduced":["0"],"last_affected":[],"package":"sm-crypto","purl":"pkg:npm/sm-crypto","source":"GHSA-vh45-f885-3848"}],"prev":{"headline":"node-tar: Uncontrolled recursion in mapHas/filesFilter allows uncatchable stack-overflow DoS via crafted long-path tar with member selection","id":"CVE-2026-73566"},"products":["sm-crypto"],"published":"2026-08-13","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-14","vendors":["JuneAndGreen"]},"summary":"Attackers can recover SM2 private keys and forge signatures due to predictable random number generation in the sm-crypto library.","url":"https://insights.sbomify.com/CVE-2026-73567/"}