Approved changes feed: RSS · Atom
cpe:2.3:a:cardano-scaling:hydra:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Cardano Scaling (2b941738-23b0-5c8e-be35-c2c1700abf0d) |
|---|---|
| Product | Hydra (ec6532ee-c195-5f90-9945-50ace58df57b) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-48886 |
vulnerable | 2026-06-08 07:29:12.162281 |
hydra-node dangerously assumes L1 event finality and does not consider failed transactions
MEDIUM (4.8)
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.
Published: 2025-06-19T14:24:58.304Z
Updated: 2025-06-23T17:36:02.598Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.