CVE-2026-53924
Smart-contract flaw allows draining escrowed SuperTokens during a disputed proposal.
Is CVE-2026-53924 being exploited?
Not confirmed. CVE-2026-53924 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.24% probability of exploitation in the next 30 days.
How severe is CVE-2026-53924?
CVE-2026-53924 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-53924?
Yes. A fix has been recorded for CVE-2026-53924. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-53924 affect?
CVE-2026-53924 affects 1Hive Gardens v2 (<0xc9d4e0dacd937364793278180551e59d93cd43f9), StreamingEscrow.syncOutflow, SuperTokens escrow. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-53924?
Upgrade to commit 0xc9d4e0dacd937364793278180551e59d93cd43f9; restrict/disable syncOutflow until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers can call syncOutflow() to transfer escrowed SuperTokens during disputes, causing permanent loss if the proposal is later rejected.
Immediate action required
- affected< 0xc9d4e0dacd937364793278180551e59d93cd43f9
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.