{"description":"Trending threats, MITRE ATT\u0026CK coverage, and detection metadata. Fed continuously.","favicon":"https://feed.craftedsignal.io/favicon-32x32.png","feed_url":"https://feed.craftedsignal.io/cpes/cpe2.3abitcoinjbitcoinj/feed.json","home_page_url":"https://feed.craftedsignal.io/","icon":"https://feed.craftedsignal.io/apple-touch-icon.png","items":[{"_cs_actors":[],"_cs_cpes":["cpe:2.3:a:bitcoinj:bitcoinj:*:*:*:*:*:*:*:*"],"_cs_cves":[{"cvss":7.3,"id":"CVE-2026-111210"}],"_cs_exploited":false,"_cs_has_poc":false,"_cs_poc_references":[],"_cs_products":["bitcoinj (\u003c= 0.17)"],"_cs_severities":["high"],"_cs_tags":[],"_cs_type":"advisory","_cs_vendors":["bitcoinj"],"content_html":"\u003cp\u003eA critical Server-Side Request Forgery (SSRF) vulnerability has been identified in the bitcoinj library, affecting all versions up to and including 0.17. The flaw is located in the Payment Request Handler component, specifically within the \u003ccode\u003eurl.openConnection\u003c/code\u003e function in \u003ccode\u003ePaymentSession.java\u003c/code\u003e. An attacker can exploit this vulnerability by manipulating the \u003ccode\u003epki_type\u003c/code\u003e argument, which is not adequately sanitized before being used to open a network connection.\u003c/p\u003e\n\u003cp\u003eThis vulnerability allows for remote exploitation, enabling an attacker to force the affected application to make arbitrary outbound HTTP requests. This can be leveraged to scan internal networks, interact with internal services that are not exposed to the public internet, or extract metadata from cloud environments. As of the time of reporting, the vulnerability has been publicly disclosed and is considered exploitable. No patch or vendor response is currently available.\u003c/p\u003e\n\u003ch2 id=\"impact\"\u003eImpact\u003c/h2\u003e\n\u003cp\u003eSuccessful exploitation of this SSRF vulnerability permits an attacker to perform requests on behalf of the application server. This can lead to unauthorized access to internal resources, exposure of sensitive infrastructure data, or potential pivoting into protected internal network segments. Organizations utilizing bitcoinj in backend systems or wallet services are at risk of unauthorized data exfiltration or service disruption if their applications are reachable by an unauthenticated attacker.\u003c/p\u003e\n\u003ch2 id=\"recommendation\"\u003eRecommendation\u003c/h2\u003e\n\u003cp\u003ePrioritize internal inventory assessment to identify applications leveraging bitcoinj 0.17 or earlier.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eRestrict outbound network access from servers running bitcoinj to only required external endpoints.\u003c/li\u003e\n\u003cli\u003eImplement strict ingress filtering and monitor for unusual outbound HTTP requests originating from application servers using this library.\u003c/li\u003e\n\u003cli\u003eIf immediate patching is not possible due to the lack of an official fix, consider implementing a Web Application Firewall (WAF) or application-layer input validation to sanitize the \u003ccode\u003epki_type\u003c/code\u003e parameter before it is processed by the Payment Request Handler.\u003c/li\u003e\n\u003cli\u003eMonitor logs for HTTP request patterns that deviate from standard wallet or payment request traffic.\u003c/li\u003e\n\u003c/ul\u003e\n","date_modified":"2026-10-16T00:41:10Z","date_published":"2026-10-16T00:41:10Z","id":"https://feed.craftedsignal.io/briefs/2026-10-bitcoinj-ssrf/","summary":"A Server-Side Request Forgery (SSRF) vulnerability in the bitcoinj Payment Request Handler component allows remote attackers to perform unauthorized requests via manipulation of the pki_type argument.","title":"SSRF Vulnerability in bitcoinj Payment Request Handler","url":"https://feed.craftedsignal.io/briefs/2026-10-bitcoinj-ssrf/"}],"language":"en","title":"CraftedSignal Threat Feed - Cpe:2.3:a:bitcoinj:bitcoinj:*:*:*:*:*:*:*:*","version":"https://jsonfeed.org/version/1.1"}