Vulnerability in org.bitcoinj:bitcoinj-core (CVE-2026-44714)
Summary
Vulnerability in org.bitcoinj:bitcoinj-core (CVE-2026-44714). Data can be tampered with by attackers. Exploitable via P2PKH. Mitigation: upgrade to 0.17.1 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44714 has been found in org.bitcoinj:bitcoinj-core.
Attackers can target a specific entry point like P2PKH over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.5/10.
What to do: upgrade org.bitcoinj:bitcoinj-core to 0.17.1 or later.
If unsure, ask your IT team or search "org.bitcoinj:bitcoinj-core CVE-2026-44714" on the vendor's site.
CVE-2026-44714 (org.bitcoinj:bitcoinj-core) — CWE-347 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: P2PKH / P2WPKH / scriptSig / scriptPubKey
Patched: 0.17.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-347) exists in org.bitcoinj:bitcoinj-core. Attackers reach the vulnerable code path via P2PKH without authentication.
Check the vendor advisory for the affected versions of org.bitcoinj:bitcoinj-core. Attack surface: P2PKH / P2WPKH / scriptSig / scriptPubKey.
Severity: High (CVSS 7.5/10). Data can be tampered with by attackers.
Update to 0.17.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで org.bitcoinj:bitcoinj-core を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.bitcoinj:bitcoinj-core to 0.17.1ステージング環境で 0.17.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com