CVE-2026-3089 — @actual-app/sync-server
Fix: actualbudget/actual#7067CVE-2026-3089 is a Path Traversal vulnerability in @actual-app/sync-server. A fix is available for @actual-app/sync-server — see the affected versions and patch details below.
Actual Sync Server 26.2.1 - Authenticated Path Traversal
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-3089.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@actual-app/sync-servernpmDescription
Description
Actual Sync Server allows authenticated users to upload files through POST /sync/upload-user-file. In versions prior to 26.3.0, improper validation of the user-controlled x-actual-file-id header means that traversal segments (../) can escape the intended directory and write files outside userFiles.
Mitigations
The vulnerability can be mitigated in prior versions by running the sync server in a filesystem sandbox.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @actual-app/sync-server | all versions | 26.3.0npm install @actual-app/sync-server@26.3.0 |
Affected Products
actualactualbudgetDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @actual-app/sync-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @actual-app/sync-server to 26.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-3089 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
Frequently Asked Questions
Is CVE-2026-3089 in your dependencies?
Find it across npm, including transitive dependencies.