# CVE-2026-45288: Marten has an SQL injection vulnerability in its full-text search regConfig parameter

> Attackers can execute arbitrary SQL commands via the regConfig parameter in Marten's full-text search APIs, potentially reading or modifying database contents.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 May 2026
- **Updated:** 30 May 2026
- **Also known as:** GHSA-vmw2-qwm8-x84c

## What is CVE-2026-45288?

CVE-2026-45288 is a critical SQL injection vulnerability in JasperFx marten, published on 28 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Marten is a .NET Transactional Document DB and Event Store on PostgreSQL. Prior to 8.36.1, Marten's full-text search APIs interpolated the user-supplied regConfig parameter directly into the generated SQL without parameterization or validation, making every code path that exposes regConfig to untrusted input a SQL injection sink. This vulnerability is fixed in 8.36.1.

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

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

2 open source packages ship an affected version, including Marten.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Marten` | NuGet | All versions | 8.37.0 |
| `Marten` | NuGet | All versions | 8.37.0 |

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

Upgrade Marten to 8.37.0 or later.

## Is CVE-2026-45288 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45288 is a critical SQL injection vulnerability in JasperFx marten, published on 28 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-45288 in the wild and no public exploit code.

Affected packages and fixed versions:
- Marten (NuGet): affected all versions; fixed in 8.37.0
- Marten (NuGet): affected all versions; fixed in 8.37.0

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

## Sources

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

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