dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-45288

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-28
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Marten's full-text search APIs directly interpolate the user-supplied regConfig parameter into generated SQL without parameterization or validation, creating a SQL injection sink. An attacker can inject arbitrary SQL through the untrusted regConfig input in any code path exposing this parameter.

MitigationUpgrade Marten to version 8.36.1 or later which implements proper parameterization of the regConfig parameter. Audit all usages of full-text search APIs to identify and validate any external regConfig input sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Marten is in use
    Search project files (.csproj, packages.config) or compiled assemblies for references to Marten (e.g., 'Marten', 'Jint'). Also check for 'using Marten;' statements in source code.
    Affected if Marten library is present in the environment
  2. Check Marten version
    Examine the referenced Marten assembly version in your project file or NuGet package reference, or query the loaded Marten assembly version at runtime via reflection on 'Marten.Services.MartenServiceCollectionExtensions' or similar entry point.
    Affected if The installed version is lower than 8.36.1
  3. Determine if full-text search is used
    Search code for calls to full-text search methods such as 'Search', 'ToSearch', 'Match', or similar APIs that accept a 'regConfig' parameter (commonly named 'regConfig', 'configuration', or 'searchConfiguration').
    Affected if Full-text search APIs are invoked and the regConfig parameter is consumed
  4. Check if regConfig receives untrusted input
    Audit all code paths that pass data to the regConfig parameter of Marten's full-text search methods. Trace whether this parameter originates from user input (HTTP request parameters, query strings, API payloads) or external sources.
    Affected if The regConfig parameter is populated with unvalidated, user-supplied data without sanitization or use of parameterized queries

You are affected if Marten version 8.36.1 or lower is in use and your code passes unsanitized user input to the regConfig parameter of Marten's full-text search APIs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade Marten to version 8.36.1 or later which implements proper parameterization of the regConfig parameter. Audit all usages of full-text search APIs to identify and validate any external regConfig input sources.

Recommended fix High confidence

8.36.1

  1. Update the Marten NuGet package in your project to version 8.36.1 or later using your NuGet package manager (e.g., dotnet add package Marten --version 8.36.1 or Update-Package Marten -Version 8.36.1)
  2. Verify the upgrade was successful by checking the installed package version in your project file or package manager
  3. If using full-text search APIs that expose the regConfig parameter, validate that your code passes trusted/validated values to this parameter (the fix ensures parameterization, but defense-in-depth is recommended)

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45288 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45288 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data