CVE-2025-48886Public exploitNetwork attack vector

Head-state desynchronization via unverified L1 deposit events

Published Jun 19, 2025 · Updated Jun 23, 2025

Improper exceptional-condition handling in Cardano Scaling Hydra before 0.22.0 allows remote authenticated users to desynchronize Hydra heads. hydra-node treats newly observed Cardano L1 deposit events as final and queues failed transactions without verifying that they changed the canonical ledger state. A participant who submits a signed deposit that later disappears in a reorganization or deliberately fails can corrupt head state and leave participants desynchronized or stale.

CVSS severity4.8
Medium
EPSS probability0.28%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper exceptional-condition handling in Cardano Scaling Hydra before 0.22.0 allows remote authenticated users to desynchronize Hydra heads. hydra-node treats newly observed Cardano L1 deposit events as final and queues failed transactions without verifying that they changed the canonical ledger state. A participant who submits a signed deposit that later disappears in a reorganization or deliberately fails can corrupt head state and leave participants desynchronized or stale.

The record

CVE
CVE-2025-48886
Published
Jun 19, 2025
Updated
Jun 23, 2025
Vendor
Cardano Scaling
Product
Hydra
Classifications
CWE-755, T1565.001
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Jun 19, 2025CVE publishedPublication date reported by the CVE source.
  2. Jun 23, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 0.22.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Cardano Scaling · Hydraversion=< 0.22.0

Published CVSS scores

4.8GitHub, Inc.CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:H/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-755Improper Handling of Exceptional Conditions
T1565.001Stored Data Manipulation

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo