# CVE-2026-50007: Actual: Shared users can perform owner-only file management actions

> Shared users can perform owner-only file management actions like deleting or resetting files due to missing authorization checks.

- **Severity:** High 7.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/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:** 7 Jul 2026
- **Updated:** 8 Jul 2026
- **Also known as:** GHSA-23vm-ffgg-qvjr

## What is CVE-2026-50007?

CVE-2026-50007 is a high-severity missing authorization vulnerability in actualbudget actual, published on 7 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Actual is an open-source personal finance application. Prior to 26.7.0, a missing authorization issue allows a shared user with user_access on a budget file to perform owner-only file management actions. A non-owner shared user can call file-management endpoints intended for higher-privilege users, including /delete-user-file, /reset-user-file, and /user-create-key, because requireFileAccess treats ordinary shared access as sufficient for file-management operations that should be restricted to the file owner or an administrator. This issue is fixed in version 26.7.0.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-50007 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-50007 is a high-severity missing authorization vulnerability in actualbudget actual, published on 7 Jul 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-50007 exists.

Affected product: actualbudget actual. 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-50007/ (Markdown: https://insights.sbomify.com/CVE-2026-50007/index.md)
```

## Sources

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

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