Bug 2564249 (CVE-2026-62162) - CVE-2026-62162 hydra: Hydra: Theft of pending deposits via improper transaction validation
Summary: CVE-2026-62162 hydra: Hydra: Theft of pending deposits via improper transacti...
Keywords:
Status: NEW
Alias: CVE-2026-62162
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2565450 2565451 2565452 2565453
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-10-30 19:11 UTC by OSIDB Bzimport
Modified: 2026-11-03 02:05 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-10-30 19:11:45 UTC
Hydra is a layer-two scalability solution for Cardano. Prior to 2.1.0, the `Claim` branch in `hydra-plutus/validators/deposit.ak` checks only that `datum.head_id` matches the attacker-controlled `redeemer.currencySymbol` and that the transaction is valid before the deposit deadline. It neither requires spending the Head state-token UTxO in the same transaction nor constrains outputs. After a deposit made through `POST /commit` is confirmed, any third party able to build a Cardano transaction can observe and consume the pending deposit UTxO before its deadline and redirect the assets to an arbitrary address. A standalone deposit spend invokes no Head validator, bypassing its safety checks; historical head-ID binding and the Aiken rewrite retained this missing invariant. The default deadline is three times depositPeriod, so the described attack applies to pending deposits before that deadline. This issue is fixed in version 2.1.0.


Note You need to log in before you can comment on or make changes to this bug.