Hydra is a layer-two scalability solution for Cardano. Prior to version 0.22.0, the process assumes L1 event finality and does not consider failed transactions. Currently, Cardano L1 is monitored for certain events which are necessary for state progression. At the moment, Hydra considers those events as finalized as soon as they are recognized by the node participants making such transactions the target of re-org attacks. The system does not currently consider the fact that failed transactions on the Cardano L1 can indeed appear in blocks because these transactions are so infrequent. This issue has been patched in version 0.22.0.
Metrics
Affected Vendors & Products
References
History
Mon, 23 Jun 2025 18:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Metrics |
ssvc
|
Thu, 19 Jun 2025 14:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | Hydra is a layer-two scalability solution for Cardano. Prior to version 0.22.0, the process assumes L1 event finality and does not consider failed transactions. Currently, Cardano L1 is monitored for certain events which are necessary for state progression. At the moment, Hydra considers those events as finalized as soon as they are recognized by the node participants making such transactions the target of re-org attacks. The system does not currently consider the fact that failed transactions on the Cardano L1 can indeed appear in blocks because these transactions are so infrequent. This issue has been patched in version 0.22.0. | |
Title | hydra-node dangerously assumes L1 event finality and does not consider failed transactions | |
Weaknesses | CWE-755 | |
References |
| |
Metrics |
cvssV3_1
|

Status: PUBLISHED
Assigner: GitHub_M
Published: 2025-06-19T14:24:58.304Z
Updated: 2025-06-23T17:36:02.598Z
Reserved: 2025-05-27T20:14:34.297Z
Link: CVE-2025-48886

Updated: 2025-06-23T17:35:54.446Z

Status : Awaiting Analysis
Published: 2025-06-19T15:15:20.473
Modified: 2025-06-23T20:16:59.783
Link: CVE-2025-48886

No data.