# CVE-2026-40906: Electric: SQL Injection via ORDER BY Parameter in Shape API

> Authenticated users can execute arbitrary SQL commands via the ORDER BY parameter, allowing full database read, write, and destruction.

- **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:** No
- **Published:** 21 Apr 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-h5rg-pxx7-r2hj

## What is CVE-2026-40906?

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

### Official description

Electric is a Postgres sync engine. From 1.1.12 to before 1.5.0, the order_by parameter in the ElectricSQL /v1/shape API is vulnerable to error-based SQL injection, allowing any authenticated user to read, write, and destroy the full contents of the underlying PostgreSQL database through crafted ORDER BY expressions. This vulnerability is fixed in 1.5.0.

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

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

It affects 1 product.


Products: Electric Sync-Service.

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

No fix has been published for CVE-2026-40906 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-40906 being exploited?

There is no known exploitation of CVE-2026-40906 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-40906 is a critical SQL injection vulnerability in electric-sql electric, published on 21 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-40906 in the wild and no public exploit code.

Affected product: electric-sql electric. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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