# CVE-2026-40163: Saltcorn has an Unauthenticated Path Traversal in sync endpoints allows arbitrary file write and directory read

> Unauthenticated attackers can exploit path traversal in Saltcorn sync endpoints to write arbitrary files and read directory contents on the server.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Apr 2026
- **Updated:** 15 Apr 2026
- **Also known as:** GHSA-32pv-mpqg-h292

## What is CVE-2026-40163?

CVE-2026-40163 is a high-severity path traversal vulnerability in saltcorn, published on 10 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-40163?

6 open source packages ship an affected version, including @saltcorn/server. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@saltcorn/server` | npm | All versions | 1.4.5 |
| `@saltcorn/server` | npm | All versions | 1.4.5 |
| `@saltcorn/server` | npm | From 1.5.0-beta.0 | 1.5.5 |
| `@saltcorn/server` | npm | From 1.5.0-beta.0 | 1.5.5 |
| `@saltcorn/server` | npm | From 1.6.0-alpha.0 | 1.6.0-beta.4 |
| `@saltcorn/server` | npm | From 1.6.0-alpha.0 | 1.6.0-beta.4 |

Products: Saltcorn Saltcorn.

## How do I fix CVE-2026-40163?

Upgrade @saltcorn/server to a fixed version for your release line: 1.4.5, 1.5.5 or 1.6.0-beta.4.

## Is CVE-2026-40163 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40163 exists.

## Other vulnerabilities in saltcorn

- [CVE-2026-41478](https://insights.sbomify.com/CVE-2026-41478/): Saltcorn: SQL Injection via Unparameterized Sync Endpoints (maxLoadedId) (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-40163 and fix it if it is affected.

What it is: CVE-2026-40163 is a high-severity path traversal vulnerability in saltcorn, published on 10 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40163 exists.

Affected packages and fixed versions:
- @saltcorn/server (npm): affected all versions; fixed in 1.4.5
- @saltcorn/server (npm): affected all versions; fixed in 1.4.5
- @saltcorn/server (npm): affected from 1.5.0-beta.0; fixed in 1.5.5
- @saltcorn/server (npm): affected from 1.5.0-beta.0; fixed in 1.5.5
- @saltcorn/server (npm): affected from 1.6.0-alpha.0; fixed in 1.6.0-beta.4
- @saltcorn/server (npm): affected from 1.6.0-alpha.0; fixed in 1.6.0-beta.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-40163/ (Markdown: https://insights.sbomify.com/CVE-2026-40163/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-40163
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-40163
- OSV: https://osv.dev/vulnerability/CVE-2026-40163

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-40163/
Summaries are generated and may contain mistakes; the official description above is the record.