CVE-2026-50007: Actual Budget missing authorization in file management endpoints

CVE-2026-50007 · Severity: info · CVSS 7.2 · Published 2026-07-07

Actual, an open-source personal finance application, contains a flaw where users invited to share a budget can perform administrative actions they should not have access to. Specifically, a guest user can delete budget files, reset synchronization data, or change encryption keys belonging to the file owner. This could lead to permanent data loss or unauthorized locking of financial records by a malicious collaborator.

Technologies: Actual Budget. Vendors: Actual Budget.

Quick answers

Is CVE-2026-50007 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-50007 being exploited in the wild.
How severe is CVE-2026-50007?
Informational severity, with a CVSS score of 7.2, published 7 July 2026.
Which products and versions are affected?
Actual Budget < 26.7.0.
Is there a fix for CVE-2026-50007?
A patch was published on 2026-05-29: Fix committed to master branch Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-50007 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-50007?
Check whether you run Actual Budget at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A missing authorization vulnerability exists in Actual Budget prior to version 26.7.0. The application's 'requireFileAccess' middleware incorrectly treated any user with shared access as having sufficient privileges for administrative file-management operations. An authenticated attacker with basic 'user_access' permissions on a shared budget can call restricted endpoints such as /delete-user-file, /reset-user-file, and /user-create-key. This allows a non-owner collaborator to delete the owner's files, reset sync states, or overwrite encryption keys. The fix introduces a stricter 'requireFileOwner' helper to enforce proper access control on these sensitive endpoints.

Affected products

  • Actual Budget Actual < 26.7.0

Timeline

  • 2026-05-29: patched: Fix committed to master branch
  • 2026-07-07: advisory: NVD and GitHub Security Advisory published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.