Actual is a local-first personal finance tool. Prior to version 26.2.1, in multi-user mode (OpenID), the sync API endpoints (/sync/*) don't verify that the authenticated user owns or has access to the file being operated on. Any authenticated user can read, modify, and overwrite any other user's budget files by providing their file ID. Version 26.2.1 patches the issue.
CVE-2026-27638
This high-severity CVE scores 7.1 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 78% 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.1
- EG Score
- 7.1(medium)
- EG Risk
- 37(Track)EG Risk 37/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 computedSeverity71% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 22%
- KEV
- Not listed
Published
February 26, 2026
Last Modified
June 17, 2026
Advisory Details (3)
Auto-updated Aug 4, 2026Missing authorization in sync endpoints allows cross-user budget file access in multi-user mode · Advisory · actualbudget/actual · GitHub
https://github.com/actualbudget/actual/security/advisories/GHSA-qmjj-p7m9-wjrvv26.2.1
Patch available: actualbudget/actual v26.2.1
https://github.com/actualbudget/actual/releases/tag/v26.2.1commit 9966c024cb75 (actualbudget/actual)
Fix landed in actualbudget/actual commit 9966c024cb75 — awaiting tagged release
https://github.com/actualbudget/actual/commit/9966c024cb75f57943193cac8e42f401efed9d08Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| @actual-app/sync-server | — | 26.2.1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 27× 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.
- 2026-09-19 14:33 UTCOSV refresh
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 19:27 UTCEPSS rescore
- 2026-09-17 19:30 UTCEPSS rescore
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-12 15:01 UTCEPSS rescore
- 2026-09-11 14:52 UTCEPSS rescore
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:11 UTCEPSS rescore
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-08-31 18:04 UTCOSV refresh
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 13:48 UTCEPSS rescore
Show 35 moreShow fewer
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 08:54 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 00:51 UTCEG score recompute
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-11 23:48 UTCEG score recompute
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-11 06:14 UTCEG score recompute
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-09 21:33 UTCEG score recompute
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 08:32 UTCEG score recompute
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-07 20:34 UTCEG score recompute
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 02:56 UTCEG score recompute
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 04:56 UTCEG score recompute
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 19:26 UTCEG score recompute
- 2026-08-02 02:26 UTCEPSS rescore
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-30 16:27 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-28 15:36 UTCEPSS rescore
- 2026-07-27 14:04 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-27638?
When was CVE-2026-27638 disclosed?
Is CVE-2026-27638 actively exploited?
What is the CVSS score of CVE-2026-27638?
How do I remediate CVE-2026-27638?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-27638
Is Your Infrastructure Affected by CVE-2026-27638?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.