CVE-2026-40163
HIGHCVE-2026-40163 is a high-severity (CVSS 8.2) Path Traversal vulnerability in @saltcorn/server. O3 Security confirms whether CVE-2026-40163 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Saltcorn has an Unauthenticated Path Traversal in sync endpoints allows arbitrary file write and directory read
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
@saltcorn/servernpmDescription
Saltcorn is an extensible, open source, no-code database application builder. Prior to 1.4.5, 1.5.5, and 1.6.0-beta.4, the POST /sync/offline_changes endpoint allows an unauthenticated attacker to create arbitrary directories and write a changes.json file with attacker-controlled JSON content anywhere on the server filesystem. The GET /sync/upload_finished endpoint allows an unauthenticated attacker to list arbitrary directory contents and read specific JSON files. This vulnerability is fixed in 1.4.5, 1.5.5, and 1.6.0-beta.4.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @saltcorn/server | all versions | 1.4.5 |
| 📦npm | @saltcorn/server | ≥ 1.5.0-beta.0&&< 1.5.5 | 1.5.5 |
| 📦npm | @saltcorn/server | ≥ 1.6.0-alpha.0&&< 1.6.0-beta.4 | 1.6.0-beta.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @saltcorn/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 @saltcorn/server to 1.4.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-40163 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 CVE-2026-40163 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 CVE-2026-40163. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-40163 in your dependencies?
O3 detects CVE-2026-40163 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.