Escrow token diversion via unchecked disputed state
Published Sep 3, 2026 · Updated Sep 3, 2026
Improper access control in 1Hive Gardens v2 allows remote attackers to divert disputed escrow tokens through the permissionless syncOutflow() path. StreamingEscrow.syncOutflow() transfers excess SuperToken balances to the proposal beneficiary without checking the escrow's disputed state, unlike claim(). A streaming proposal must already be challenged; if it is later rejected, drainToStrategy() cannot recover the transferred tokens.
Summary
What happened
Improper access control in 1Hive Gardens v2 allows remote attackers to divert disputed escrow tokens through the permissionless syncOutflow() path. StreamingEscrow.syncOutflow() transfers excess SuperToken balances to the proposal beneficiary without checking the escrow's disputed state, unlike claim(). A streaming proposal must already be challenged; if it is later rejected, drainToStrategy() cannot recover the transferred tokens.
The record
- CVE
- CVE-2026-53924
- Published
- Sep 3, 2026
- Updated
- Sep 3, 2026
- Vendor
- 1Hive
- Product
- Gardens v2
- Classifications
- CWE-284, T1657
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 3, 2026CVE publishedPublication date reported by the CVE source.
- Sep 3, 2026Record 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=< 0xc9d4e0dacd937364793278180551e59d93cd43f9
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.
Public exploit references
No public exploit references are available in this record.
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