Skip to main content
VulnerabilityPublished

CVE-2026-62162: cardano-scaling hydra · Missing Authorization

Affects cardano-scaling hydraSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.2 High : upgrade to 2.1.0 soon.

Data as of 30 Oct 2026, 19:03 UTC

CVSS 4.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.08.2
Patch
Available – fixed in 2.1.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade hydra and cardano-scaling/hydra to 2.1.0.

Affected software

ProductAffectedFixed in
cardano-scalinghydraAffected
  • <2.1.0
Fixed in
  • 2.1.0
GitHubcardano-scaling/hydrapkg:github/cardano-scaling/hydraOther threatsAffected
  • <2.1.0
Fixed in
  • 2.1.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Hydra to version 2.1.0 or later, where this missing authorization vulnerability is fixed. No other mitigation is required as the fix enforces proper spending of the Head state-token UTxO and output constraints to prevent unauthorized consumption of pending deposits.

Description

CVE-2026-62162 is a missing authorization vulnerability in the Cardano layer-two scaling solution Hydra prior to version 2.1.0. The flaw allows third parties to consume pending deposit UTxOs before the deposit deadline without proper authorization, redirecting assets to arbitrary addresses. This occurs because the validator does not require spending the Head state-token UTxO or constrain outputs, enabling bypass of safety checks. The issue is fixed in Hydra version 2.1.0.

References

Community reviews

Loading reviews…