CVE-2026-57445
Received Received - Intake

StreamingEscrow Dispute Path Drains Escrow Balance in Gardens v2

Publication date: 2026-09-03

Last updated on: 2026-09-03

Assigner: GitHub, Inc.

Description
Gardens v2 is a modular governance framework that enables communities to create and manage multiple governance pools with customizable parameters and voting mechanisms. In dfba919e218e20d52db9f7b2e8d292d45a46c91b and prior, normal beneficiary payout paths in StreamingEscrow preserve depositAmount() while an active stream needs an escrow reserve. However, the approve-side dispute resolution path drains the whole available escrow balance to the proposal beneficiary. At time of publication, there are no publicly known patches.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-03
Last Modified
2026-09-03
Generated
2026-09-03
AI Q&A
2026-09-03
EPSS Evaluated
N/A
NVD
CVE-2026-57445
EUVD
EUVD-2026-70523

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
1hive gardens_v2 *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-703 The product does not properly anticipate or handle exceptional conditions that rarely occur during normal operation of the product.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a high-severity vulnerability in the Gardens v2 smart contracts where the approve-side dispute resolution process incorrectly drains the active streaming escrow reserve. Normally, the escrow reserve is preserved during active streams, but when a streaming proposal is disputed and later resolved as approved, the system fully drains the entire available escrow balance to the beneficiary. This includes funds that should remain reserved for the active stream, such as the deposit amount and a 50 bps buffer.

Detection Guidance

This vulnerability is specific to the Gardens v2 smart contracts and cannot be detected using standard network or system commands. It requires auditing the smart contract code for the presence of the flawed dispute resolution logic in StreamingEscrow. Look for functions like _handleStreamingResolution and drainToBeneficiary that do not preserve the escrow reserve during approve-side resolution.

Impact Analysis

An attacker could exploit this by creating a disputed streaming proposal, topping up the escrow during rebalance, and then triggering an approve-side resolution to drain the reserve. This allows beneficiaries to receive more funds than intended while compromising the stream's health. The impact is limited to the escrow reserve and does not affect Superfluid protocol-held deposits.

Compliance Impact

This vulnerability does not directly affect compliance with GDPR or HIPAA as it pertains to data protection or privacy. However, it could indirectly impact compliance if the drained escrow funds were intended for regulatory-mandated financial reserves or audits, potentially leading to financial discrepancies or audit failures.

Mitigation Strategies

Review and update the StreamingEscrow contract to use a reserve-preserving drain function during approve-side dispute resolution. Ensure the escrow retains the required active-stream reserve by modifying the resolution logic to avoid draining the entire balance.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-57445. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart