{"answers":{"affected":"2 open source packages ship an affected version, including altcha.","exploited":"There is no known exploitation of CVE-2025-65849 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-65849 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-65849 is a critical vulnerability in n/a, published on 8 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-65849 and fix it if it is affected.\n\nWhat it is: CVE-2025-65849 is a critical vulnerability in n/a, published on 8 Dec 2025. 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-2025-65849 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- altcha (npm): affected from 0.8.0 up to 2.2.4; no fix listed\n- altcha (npm): affected from 0.8.0 up to 2.2.4; no fix listed\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-2025-65849/ (Markdown: https://insights.sbomify.com/CVE-2025-65849/index.md)","id":"CVE-2025-65849","markdown":"https://insights.sbomify.com/CVE-2025-65849/index.md","name":"CVE-2025-65849","record":{"aliases":["GHSA-mpmc-qchh-r9q8"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Altcha PoW library","requires_auth":"none","summary":"Attackers can bypass Altcha Proof-of-Work obfuscation to recover nonces, defeating bot protection mechanisms in npm packages.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cisa-adp","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-327","name":"Use of a Broken or Risky Cryptographic Algorithm"}],"description":"A cryptanalytic break in Altcha Proof-of-Work obfuscation mode version 0.8.0 and later allows for remote visitors to recover the Proof-of-Work nonce in constant time via mathematical deduction. NOTE: this is disputed by the Supplier because the product's objective is \"to discourage automated scraping / bots, not guarantee resistance to determined attackers.\" The documentation states “the goal is not to provide a secure cryptographic algorithm but to use a proof-of-work mechanism that allows any capable device to decrypt the hidden data.”","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":false,"headline":"Altcha Proof-of-Work obfuscation mode cryptanalytic break","id":"CVE-2025-65849","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"weak_cryptography","year":"2025"},"n_packages":2,"n_references":3,"next":{"headline":"MineAdmin has an insecure default password","id":"CVE-2025-65854"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0.8.0"],"last_affected":["2.2.4"],"package":"altcha","purl":null,"source":"GHSA-mpmc-qchh-r9q8"},{"ecosystem":"npm","fixed":[],"introduced":["0.8.0"],"last_affected":["2.2.4"],"package":"altcha","purl":"pkg:npm/altcha","source":"GHSA-mpmc-qchh-r9q8"}],"prev":{"headline":"File upload in n/a","id":"CVE-2025-65844"},"products":["n/a"],"published":"2025-12-08","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":"2025-12-11","vendors":["n/a"]},"summary":"Attackers can bypass Altcha Proof-of-Work obfuscation to recover nonces, defeating bot protection mechanisms in npm packages.","url":"https://insights.sbomify.com/CVE-2025-65849/"}