GHSA-27vg-33gh-4hwg
GHSA-27vg-33gh-4hwg is a Path Traversal vulnerability in @actual-app/sync-server. O3 Security confirms whether GHSA-27vg-33gh-4hwg is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Actual Sync Server has an Authenticated Path Traversal
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
@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.0 |
Detection & 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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 GHSA-27vg-33gh-4hwg is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-27vg-33gh-4hwg is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-27vg-33gh-4hwg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-27vg-33gh-4hwg in your dependencies?
O3 detects GHSA-27vg-33gh-4hwg across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.