# CVE-2026-55658: Gardens v2: StreamingEscrow buffer drains to the proposal beneficiary on cancel via the permissionless claim()

> Attackers can steal pool funds by submitting a streaming proposal and canceling it, causing the escrow buffer to be sent to the beneficiary instead of the pool.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Sep 2026
- **Updated:** 5 Sep 2026

## What is CVE-2026-55658?

CVE-2026-55658 is a high-severity vulnerability in 1Hive gardens-v2, published on 3 Sep 2026. Any signed-in user can exploit it over the network, 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 3e595f3 and prior, when a streaming proposal is funded, the cluster of streaming contracts moves real pool funds into the proposal's StreamingEscrow to back the Superfluid constant flow agreement (the CFA deposit, plus a 0.5 percent margin). cancelProposal then zeroes the escrow's GDA member units but never reclaims that parked balance, and the permissionless claim() forwards the escrow's entire balance, including the pool funded buffer, to the beneficiary. The beneficiary is chosen by the proposal submitter and defaults to the submitter. The only path that returns escrow funds to the pool is drainToStrategy, which is onlyStrategy and is reached solely from the dispute reject ruling, never from cancel or natural completion. At time of publication, there are no publicly known patches.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-55658 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55658 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-55658 is a high-severity vulnerability in 1Hive gardens-v2, published on 3 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55658 exists.

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-55658/ (Markdown: https://insights.sbomify.com/CVE-2026-55658/index.md)
```

## Sources

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

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