Verified chain corruption via cross-batch transition index
Published Dec 4, 2025 · Updated Dec 5, 2025
Improper array-index validation in Taiko Alethia 2.3.1 and earlier allows remote attackers to corrupt the verified chain pointer. TaikoInbox._verifyBatches updates tid for the current batch before verification completes, then stores that index on the preceding verified batch when the loop stops. A cooldown or invalidated transition must interrupt a linked multi-batch verification sequence, causing the preceding batch to reference a transition from the next batch.
Summary
What happened
Improper array-index validation in Taiko Alethia 2.3.1 and earlier allows remote attackers to corrupt the verified chain pointer. TaikoInbox._verifyBatches updates tid for the current batch before verification completes, then stores that index on the preceding verified batch when the loop stops. A cooldown or invalidated transition must interrupt a linked multi-batch verification sequence, causing the preceding batch to reference a transition from the next batch.
The record
- CVE
- CVE-2025-66559
- Published
- Dec 4, 2025
- Updated
- Dec 5, 2025
- Vendor
- Taiko
- Product
- taiko-mono
- Classifications
- CWE-129
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 4, 2025CVE publishedPublication date reported by the CVE source.
- Dec 5, 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.
- Affected versionversion=<= 2.3.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
Public exploit references
- InboxTest_LinkedProof regression testproof of concept · demonstrated
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