# CVE-2026-110772: Sure 0.7.0 through 0.7.6-alpha.6 Missing Authorization via Transaction Bulk Update

> Authenticated users can modify other members' transaction data by bypassing account sharing permissions in the bulk update controller.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA: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:** 14 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-v84h-gfv8-x79x

## What is CVE-2026-110772?

CVE-2026-110772 is a medium-severity missing authorization vulnerability in we-promise sure, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Sure 0.7.0 through 0.7.6-alpha.6 contains a missing authorization vulnerability in Transactions::BulkUpdatesController#create that allows family members to bypass account sharing permissions. Authenticated members with read_only or no share can submit arbitrary entry_ids to modify other members' transaction dates, names, notes, categories, merchants and tags, corrupting budgets and reports.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-110772 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110772 is a medium-severity missing authorization vulnerability in we-promise sure, published on 14 Oct 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-110772 exists.

Affected product: we-promise sure. 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-110772/ (Markdown: https://insights.sbomify.com/CVE-2026-110772/index.md)
```

## Sources

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

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