{"answers":{"affected":"2 open source packages ship an affected version, including sm-crypto. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-23965 in the wild and no public exploit code.","fix":"Upgrade sm-crypto to 0.4.0 or later.","what":"CVE-2026-23965 is a high-severity vulnerability in JuneAndGreen sm-crypto, published on 22 Jan 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-23965 and fix it if it is affected.\n\nWhat it is: CVE-2026-23965 is a high-severity vulnerability in JuneAndGreen sm-crypto, published on 22 Jan 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-23965 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- sm-crypto (npm): affected all versions; fixed in 0.4.0\n- sm-crypto (npm): affected all versions; fixed in 0.4.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-23965/ (Markdown: https://insights.sbomify.com/CVE-2026-23965/index.md)","id":"CVE-2026-23965","markdown":"https://insights.sbomify.com/CVE-2026-23965/index.md","name":"CVE-2026-23965","record":{"aliases":["GHSA-hpwg-xg7m-3p6m"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript crypto library","requires_auth":"none","summary":"Attackers can forge valid SM2 signatures for arbitrary public keys, bypassing authentication or integrity checks in applications using this JavaScript library.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"sm-crypto","vendor":"juneandgreen"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"sm-crypto provides JavaScript implementations of the Chinese cryptographic algorithms SM2, SM3, and SM4. A signature forgery vulnerability exists in the SM2 signature verification logic of sm-crypto prior to version 0.4.0. Under default configurations, an attacker can forge valid signatures for arbitrary public keys. If the message space contains sufficient redundancy, the attacker can fix the prefix of the message associated with the forged signature to satisfy specific formatting requirements. Version 0.4.0 patches the issue.","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 Affected by Signature Forgery in SM2-DSA","id":"CVE-2026-23965","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":"sm-crypto Affected by Private Key Recovery in SM2-PKE","id":"CVE-2026-23966"},"packages":[{"ecosystem":"npm","fixed":["0.4.0"],"introduced":["0"],"last_affected":[],"package":"sm-crypto","purl":null,"source":"GHSA-hpwg-xg7m-3p6m"},{"ecosystem":"npm","fixed":["0.4.0"],"introduced":["0"],"last_affected":[],"package":"sm-crypto","purl":"pkg:npm/sm-crypto","source":"GHSA-hpwg-xg7m-3p6m"}],"prev":{"headline":"Mastodon has insufficient access control to push notification settings","id":"CVE-2026-23964"},"products":["sm-crypto"],"published":"2026-01-22","related":[{"cvss_score":9.1,"headline":"sm-crypto Affected by Private Key Recovery in SM2-PKE","id":"CVE-2026-23966","kev_date_added":null,"published":"2026-01-22"},{"cvss_score":7.5,"headline":"sm-crypto Affected by Signature Malleability in SM2-DSA","id":"CVE-2026-23967","kev_date_added":null,"published":"2026-01-22"}],"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":"US public information, NVD API terms","name":"NVD"},{"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":"partial"},"state":"PUBLISHED","updated":"2026-01-22","vendors":["JuneAndGreen"]},"summary":"Attackers can forge valid SM2 signatures for arbitrary public keys, bypassing authentication or integrity checks in applications using this JavaScript library.","url":"https://insights.sbomify.com/CVE-2026-23965/"}