CVE-2026-62162

published 30 Oct 2026 · updated 30 Oct 2026

Hydra: Deposit Claim omits Head state-token spending requirement

8.2HighCVSS 8.2EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
cardano-scaling<2.1.0

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-62162 severity on Zeptric[![CVE-2026-62162](https://zeptric.io/badge/cve/CVE-2026-62162.svg)](https://zeptric.io/cve/CVE-2026-62162)