# CVE-2026-41478: Saltcorn: SQL Injection via Unparameterized Sync Endpoints (maxLoadedId)

> Authenticated low-privilege users can inject SQL via sync endpoints to exfiltrate sensitive data or modify the database.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Apr 2026
- **Updated:** 27 Apr 2026
- **Also known as:** GHSA-jp74-mfrx-3qvh

## What is CVE-2026-41478?

CVE-2026-41478 is a critical SQL injection vulnerability in saltcorn, published on 24 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Saltcorn is an extensible, open source, no-code database application builder. Prior to 1.4.6, 1.5.6, and 1.6.0-beta.5, a SQL injection vulnerability in Saltcorn’s mobile-sync routes allows any authenticated low-privilege user with read access to at least one table to inject arbitrary SQL through sync parameters. This can lead to full database exfiltration, including admin password hashes and configuration secrets, and may also enable database modification or destruction depending on the backend. This vulnerability is fixed in 1.4.6, 1.5.6, and 1.6.0-beta.5.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

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.6 |
| `@saltcorn/server` | npm | All versions | 1.4.6 |
| `@saltcorn/server` | npm | From 1.5.0-beta.0 | 1.5.6 |
| `@saltcorn/server` | npm | From 1.5.0-beta.0 | 1.5.6 |
| `@saltcorn/server` | npm | From 1.6.0-alpha.0 | 1.6.0-beta.5 |
| `@saltcorn/server` | npm | From 1.6.0-alpha.0 | 1.6.0-beta.5 |

Products: Saltcorn Saltcorn.

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

Upgrade @saltcorn/server to a fixed version for your release line: 1.4.6, 1.5.6 or 1.6.0-beta.5.

## Is CVE-2026-41478 being exploited?

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

## Other vulnerabilities in saltcorn

- [CVE-2026-40163](https://insights.sbomify.com/CVE-2026-40163/): Saltcorn has an Unauthenticated Path Traversal in sync endpoints allows arbitrary file write and directory read (high 8.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41478 is a critical SQL injection vulnerability in saltcorn, published on 24 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41478 exists.

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

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-41478/ (Markdown: https://insights.sbomify.com/CVE-2026-41478/index.md)
```

## Sources

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

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