Which BTCPay Server versions are vulnerable to hot wallet drains in 2026?

BTCPay Server versions 2.4.1 and older are currently vulnerable to hot wallet drains, while the latest 2.4.7 release has been confirmed as secure. Merchants using the platform must update immediately to protect their funds from unauthorized withdrawals linked to this exploit.
Which BTCPay Server versions are vulnerable to hot wallet drains in 2026?

Investigations by the BTCPay Server development team in early 2026 have confirmed that hot wallet drains are actively affecting users running version 2.4.1 or older. The team reports that there have been no credible attacks or successful exploits identified on the latest 2.4.7 release. This makes upgrading to the newest software iteration the primary defense for merchants and businesses utilizing the self-hosted payment processor to manage Bitcoin transactions.

The investigation was launched following a series of reports from the community regarding unexpected fund outflows from hot wallets integrated with the server software. While the core BTCPay Server architecture is designed for security, these older versions appear to contain a specific vulnerability that allows attackers to bypass certain spend authorizations. The team has not released the full technical details of the exploit yet to prevent further malicious actors from targeting unpatched servers, but they emphasized that the fix is already live in the current stable build.

For US-based merchants, this security alert highlights the operational risks associated with self-custodial payment infrastructure. As the regulatory landscape in 2026 places higher emphasis on consumer protection and the security of digital asset service providers, maintaining outdated software could lead to both financial loss and potential liability. This incident underscores the importance of automated update cycles for critical financial infrastructure in the decentralized ecosystem.

Market-wide, while this vulnerability does not impact the Bitcoin protocol itself, it serves as a cautionary tale for the burgeoning DeFi and merchant adoption sectors. Investors and users should watch for a comprehensive post-mortem from the BTCPay team to see if the vulnerability originated in a third-party dependency. For now, the immediate focus remains on migrating the user base to version 2.4.7 to prevent further losses across the merchant network.

Editorial method

This report is based on the linked source and is labeled with its publication date, provider, category and market-impact assessment. Market interpretation is informational, not investment advice.