CVE-2026-50007

HIGHPre-NVD 7.27.2
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 84% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
7.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.2Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.2
EG Score
7.2(medium)
EG Risk
48(Track*)
EG Risk 48/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity72% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

July 7, 2026

Last Modified

July 8, 2026

Advisory Details (4)

Auto-updated Jul 7, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github.
github Patch Available🟡 PoC Available

Shared users can perform owner-only file management actions · Advisory · actualbudget/actual · GitHub

https://github.com/actualbudget/actual/security/advisories/GHSA-23vm-ffgg-qvjr
github_pr

bring release branch up to date

Fix merged in actualbudget/actual PR #8333 on 2026-06-25 — awaiting tagged release

https://github.com/actualbudget/actual/pull/8333
github_pr

[AI] Restrict owner-only sync-server file management endpoints

Fix merged in actualbudget/actual PR #7977 on 2026-05-29 — awaiting tagged release

https://github.com/actualbudget/actual/pull/7977
github_commit

commit 18a8dc03c48e (actualbudget/actual)

Fix landed in actualbudget/actual commit 18a8dc03c48e — awaiting tagged release

https://github.com/actualbudget/actual/commit/18a8dc03c48eeb2e8252669a80673e6a9933b5fd

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 43× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-03 10:36 UTCEPSS rescore
  2. 2026-08-02 06:26 UTCEG score recompute
  3. 2026-08-02 02:27 UTCEPSS rescore
  4. 2026-08-01 05:45 UTCEG score recompute
  5. 2026-08-01 04:16 UTCEPSS rescore
  6. 2026-07-31 04:34 UTCEG score recompute
  7. 2026-07-30 16:28 UTCEPSS rescore
  8. 2026-07-30 16:14 UTCEG score recompute
  9. 2026-07-30 02:54 UTCEG score recompute
  10. 2026-07-30 01:30 UTCEPSS rescore
  11. 2026-07-29 02:16 UTCEG score recompute
  12. 2026-07-28 15:37 UTCEPSS rescore
  13. 2026-07-28 01:34 UTCEG score recompute
  14. 2026-07-27 00:55 UTCEG score recompute
  15. 2026-07-26 14:54 UTCEPSS rescore
  16. 2026-07-26 12:35 UTCEG score recompute
  17. 2026-07-25 14:18 UTCEPSS rescore
  18. 2026-07-24 14:18 UTCEPSS rescore
  19. 2026-07-23 14:18 UTCEPSS rescore
  20. 2026-07-23 03:18 UTCEG score recompute
  21. 2026-07-22 14:08 UTCEPSS rescore
  22. 2026-07-21 15:25 UTCEPSS rescore
  23. 2026-07-20 17:08 UTCEPSS rescore
  24. 2026-07-19 14:31 UTCEPSS rescore
  25. 2026-07-19 14:31 UTCEPSS rescore
Show 18 more
  1. 2026-07-19 02:29 UTCEPSS rescore
  2. 2026-07-18 10:04 UTCEPSS rescore
  3. 2026-07-16 17:03 UTCEPSS rescore
  4. 2026-07-15 16:57 UTCEPSS rescore
  5. 2026-07-15 16:57 UTCEPSS rescore
  6. 2026-07-15 02:00 UTCEPSS rescore
  7. 2026-07-15 02:00 UTCEPSS rescore
  8. 2026-07-13 22:31 UTCEPSS rescore
  9. 2026-07-13 06:13 UTCEPSS rescore
  10. 2026-07-13 06:13 UTCEPSS rescore
  11. 2026-07-12 05:46 UTCEPSS rescore
  12. 2026-07-11 08:27 UTCEPSS rescore
  13. 2026-07-11 08:27 UTCEPSS rescore
  14. 2026-07-09 19:10 UTCEPSS rescore
  15. 2026-07-09 19:10 UTCEPSS rescore
  16. 2026-07-08 15:16 UTCEPSS rescore
  17. 2026-07-07 21:03 UTCEG score recompute
  18. 2026-07-07 21:01 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-50007?
CVE-2026-50007 is a high vulnerability published on July 7, 2026. 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,…
When was CVE-2026-50007 disclosed?
CVE-2026-50007 was first published in the National Vulnerability Database on July 7, 2026, with the most recent update on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50007 actively exploited?
CVE-2026-50007 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 84.0% of all scored CVEs.
What is the CVSS score of CVE-2026-50007?
CVE-2026-50007 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2026-50007?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50007, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-50007

Explore →

Is Your Infrastructure Affected by CVE-2026-50007?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.