# CVE-2026-53924: Gardens v2: Permissionless syncOutflow bypasses streaming proposal disputes

> Attackers can bypass dispute checks to prematurely transfer escrowed tokens, causing permanent loss if the proposal is later rejected.

- **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

## What is CVE-2026-53924?

CVE-2026-53924 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. Prior to 0xc9d4e0dacd937364793278180551e59d93cd43f9, StreamingEscrow.claim() correctly rejects withdrawals while an escrow is disputed, but the permissionless syncOutflow() path performs the same excess-balance transfer without checking disputed. After a streaming proposal is challenged, anyone can call syncOutflow() to transfer escrowed SuperTokens to the proposal beneficiary while the dispute is pending. If the proposal is later rejected, those tokens cannot be recovered by drainToStrategy(). This issue has been patched in 0xc9d4e0dacd937364793278180551e59d93cd43f9.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-53924 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-53924 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-53924 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-53924/ (Markdown: https://insights.sbomify.com/CVE-2026-53924/index.md)
```

## Sources

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

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