# CVE-2026-57445: Gardens v2: Approve-side dispute resolution drains active streaming escrow reserve

> Attackers can drain escrow reserves during dispute resolution, causing financial loss in Gardens v2 governance pools.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Sep 2026
- **Updated:** 3 Sep 2026
- **Also known as:** GHSA-3xpr-2mm7-77j7

## What is CVE-2026-57445?

CVE-2026-57445 is a high-severity vulnerability in 1Hive gardens-v2, published on 3 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-703 (Improper Check or Handling of Exceptional Conditions)

## Which versions are affected by CVE-2026-57445?


## How do I fix CVE-2026-57445?

No fix has been published for CVE-2026-57445 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-57445 being exploited?

There is no known exploitation of CVE-2026-57445 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-57445 and fix it if it is affected.

What it is: CVE-2026-57445 is a high-severity vulnerability in 1Hive gardens-v2, published on 3 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-57445 in the wild and no public exploit code.

Affected product: 1Hive gardens-v2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-57445/ (Markdown: https://insights.sbomify.com/CVE-2026-57445/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-57445
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-57445
- OSV: https://osv.dev/vulnerability/CVE-2026-57445

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-57445/
Summaries are generated and may contain mistakes; the official description above is the record.