{"answers":{"affected":"2 open source packages ship an affected version, including org.bitcoinj:bitcoinj-core.","exploited":"There is no known exploitation of CVE-2026-44714 in the wild and no public exploit code.","fix":"Upgrade org.bitcoinj:bitcoinj-core to 0.17.1 or later.","what":"CVE-2026-44714 is a high-severity authentication bypass vulnerability in bitcoinj, published on 15 May 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-44714 and fix it if it is affected.\n\nWhat it is: CVE-2026-44714 is a high-severity authentication bypass vulnerability in bitcoinj, published on 15 May 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-44714 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.bitcoinj:bitcoinj-core (Maven): affected from 0.15; fixed in 0.17.1\n- org.bitcoinj:bitcoinj-core (Maven): affected from 0.15; fixed in 0.17.1\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-44714/ (Markdown: https://insights.sbomify.com/CVE-2026-44714/index.md)","id":"CVE-2026-44714","markdown":"https://insights.sbomify.com/CVE-2026-44714/index.md","name":"CVE-2026-44714","record":{"aliases":["GHSA-hfcf-v2f8-x9pc"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Bitcoin protocol library","requires_auth":"none","summary":"Attackers can bypass local script verification for P2PKH and P2WPKH outputs by using arbitrary keypairs, undermining transaction validation integrity.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"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":"The bitcoinj library is a Java implementation of the Bitcoin protocol. Prior to 0.17.1, ScriptExecution.correctlySpends() contains two fast-path verification bugs for standard P2PKH and native P2WPKH spends in core/src/main/java/org/bitcoinj/script/ScriptExecution.java. In both branches, bitcoinj verifies an attacker-controlled signature/public-key pair but fails to verify that the public key is the one committed to by the output being spent. As a result, any attacker keypair can satisfy bitcoinj's local verification for arbitrary P2PKH and P2WPKH outputs. This vulnerability is fixed in 0.17.1.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":"2026-10-21","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-10-21T00:09:39Z","kind":"github_poc","ref":"https://github.com/dntaskmehow/BABEF","stars":0,"title":"This framework has been RE-WEAPONIZED \u0026 exploits CVE-2026-44714, a critical signature verification flaw in the bitcoinj library (Java implementation of the Bitcoin protocol). Unpatched applications are vulnerable to transaction spoofing, allowing attackers to:"}],"tier":"poc_unverified"},"has_fix":true,"headline":"bitcoinj: ScriptExecution P2PKH/P2WPKH Verification Bypass","id":"CVE-2026-44714","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"OpenMRS has Broken Access Control in HL7 Configuration","id":"CVE-2026-44715"},"packages":[{"ecosystem":"Maven","fixed":["0.17.1"],"introduced":["0.15"],"last_affected":[],"package":"org.bitcoinj:bitcoinj-core","purl":null,"source":"GHSA-hfcf-v2f8-x9pc"},{"ecosystem":"Maven","fixed":["0.17.1"],"introduced":["0.15"],"last_affected":[],"package":"org.bitcoinj:bitcoinj-core","purl":"pkg:maven/org.bitcoinj/bitcoinj-core","source":"GHSA-hfcf-v2f8-x9pc"}],"prev":{"headline":"pam_usb: Command injection via $TMUX environment variable leads to RCE as root","id":"CVE-2026-44713"},"products":["bitcoinj"],"published":"2026-05-15","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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-16","vendors":["bitcoinj"]},"summary":"Attackers can bypass local script verification for P2PKH and P2WPKH outputs by using arbitrary keypairs, undermining transaction validation integrity.","url":"https://insights.sbomify.com/CVE-2026-44714/"}