GHSA-8986-V76Q-8VR2

Overview

P2PKH has 20 bytes just like P2SH. We protect against revealing P2PKH deposits by manually assembling the expected P2SH script in the smart contract and comparing hashes. However, we missed the case when the attacker embeds a valid P2SH inside of P2PKH as an output script. bitcoin-spv library extracts the P2SH from P2PKH and we treat it as a valid P2SH output.

This does not lead to stealing funds but can lead to protocol insolvency.

The off-chain client handles this case correctly, but the problem is in the optimistic minting bot. The bot assumes that if the funding TX exists on Bitcoin with the right amount and it was successfully revealed, the transaction is valid.

https://bugs.immunefi.com/magnus/672/projects/502/bug-bounty/reports/55982

Steps

Since there is a 24-hour governance delay on upgrading the Bridge smart contract, we are going to pause optimistic minting.

1. Pause optimistic minting.
2. Deploy new Bridge implementation with Deposit library containing a fix, WITHOUT VERIFYING THE CODE on Etherscan.
3. Schedule upgrade transaction.
4. After 24 hours, finalize upgrade.
5. Unpause optimistic minting.

GHSA-8986-V76Q-8VR2 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.8.2); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is GHSA-8986-V76Q-8VR2? GHSA-8986-V76Q-8VR2 is a high-severity security vulnerability in @keep-network/tbtc-v2 (npm), affecting versions <= 1.8.1. It is fixed in 1.8.2.
2. How severe is GHSA-8986-V76Q-8VR2? GHSA-8986-V76Q-8VR2 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of @keep-network/tbtc-v2 are affected by GHSA-8986-V76Q-8VR2? @keep-network/tbtc-v2 (npm) versions <= 1.8.1 is affected.
4. Is there a fix for GHSA-8986-V76Q-8VR2? Yes. GHSA-8986-V76Q-8VR2 is fixed in 1.8.2. Upgrade to this version or later.
5. Is GHSA-8986-V76Q-8VR2 exploitable, and should I be worried? Whether GHSA-8986-V76Q-8VR2 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-8986-V76Q-8VR2 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-8986-V76Q-8VR2? Upgrade @keep-network/tbtc-v2 to 1.8.2 or later.