<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 28 Sep 2026 10:12:32 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-45288</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-45288</link>
      <description>&lt;p&gt;Marten is a .NET Transactional Document DB and Event Store on PostgreSQL. Prior to 8.36.1, Marten&amp;#39;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Marten is a .NET Transactional Document DB and Event Store on PostgreSQL. Prior to 8.36.1, Marten&amp;#39;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-45288</guid>
    </item>
    <item>
      <title>GHSA-vmw2-qwm8-x84c — Marten has an injection vulnerability in its full-text search regConfig parameter</title>
      <link>https://db.gcve.eu/vuln/ghsa-vmw2-qwm8-x84c</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; NuGet: Marten&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;Marten&amp;#39;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.&lt;/p&gt;
&lt;p&gt;## Affected APIs&lt;/p&gt;
&lt;p&gt;- `IQuerySession.SearchAsync&amp;lt;T&amp;gt;(string searchTerm, string regConfig, ...)`
- `IQuerySession.PlainTextSearchAsync&amp;lt;T&amp;gt;(...)`
- `IQuerySession.PhraseSearchAsync&amp;lt;T&amp;gt;(...)`
- `IQuerySession.WebStyleSearchAsync&amp;lt;T&amp;gt;(...)`
- `IQuerySession.PrefixSearchAsync&amp;lt;T&amp;gt;(...)`
- `IQueryable&amp;lt;T&amp;gt;.Where(x =&amp;gt; x.Search(term, regConfig))` and the matching `PlainTextSearch` / `PhraseSearch` / `WebStyleSearch` / `PrefixSearch` extension methods&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;In the affected versions, [`FullTextWhereFragment`](https://github.com/JasperFx/marten/blob/master/src/Marten/Linq/SqlGeneration/Filters/FullTextWhereFragment.cs) renders the WHERE-clause SQL by string interpolation:&lt;/p&gt;
&lt;p&gt;```csharp
private string Sql =&amp;gt;
    $&amp;#34;to_tsvector(&amp;#39;{_regConfig}&amp;#39;::regconfig, {_dataConfig}) @@ {_searchFunction}(&amp;#39;{_regConfig}&amp;#39;::regconfig, ?)&amp;#34;;
```&lt;/p&gt;
&lt;p&gt;`_regConfig` arrives unchanged from the public API surface above. Any value containing a single quote terminates the SQL literal and lets an attacker append arbitrary PostgreSQL.&lt;/p&gt;
&lt;p&gt;### Confirmed exploit shapes (with `regConfig` set to attacker-controlled input)&lt;/p&gt;
&lt;p&gt;| Goal | Payload |
| --- | --- |
| Time-based blind | `english&amp;#39;::text); SELECT pg_sleep(5); --` |
| Information disclosure | `english&amp;#39;; SELECT version(); --` |
|…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; NuGet: Marten&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;Marten&amp;#39;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.&lt;/p&gt;
&lt;p&gt;## Affected APIs&lt;/p&gt;
&lt;p&gt;- `IQuerySession.SearchAsync&amp;lt;T&amp;gt;(string searchTerm, string regConfig, ...)`
- `IQuerySession.PlainTextSearchAsync&amp;lt;T&amp;gt;(...)`
- `IQuerySession.PhraseSearchAsync&amp;lt;T&amp;gt;(...)`
- `IQuerySession.WebStyleSearchAsync&amp;lt;T&amp;gt;(...)`
- `IQuerySession.PrefixSearchAsync&amp;lt;T&amp;gt;(...)`
- `IQueryable&amp;lt;T&amp;gt;.Where(x =&amp;gt; x.Search(term, regConfig))` and the matching `PlainTextSearch` / `PhraseSearch` / `WebStyleSearch` / `PrefixSearch` extension methods&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;In the affected versions, [`FullTextWhereFragment`](https://github.com/JasperFx/marten/blob/master/src/Marten/Linq/SqlGeneration/Filters/FullTextWhereFragment.cs) renders the WHERE-clause SQL by string interpolation:&lt;/p&gt;
&lt;p&gt;```csharp
private string Sql =&amp;gt;
    $&amp;#34;to_tsvector(&amp;#39;{_regConfig}&amp;#39;::regconfig, {_dataConfig}) @@ {_searchFunction}(&amp;#39;{_regConfig}&amp;#39;::regconfig, ?)&amp;#34;;
```&lt;/p&gt;
&lt;p&gt;`_regConfig` arrives unchanged from the public API surface above. Any value containing a single quote terminates the SQL literal and lets an attacker append arbitrary PostgreSQL.&lt;/p&gt;
&lt;p&gt;### Confirmed exploit shapes (with `regConfig` set to attacker-controlled input)&lt;/p&gt;
&lt;p&gt;| Goal | Payload |
| --- | --- |
| Time-based blind | `english&amp;#39;::text); SELECT pg_sleep(5); --` |
| Information disclosure | `english&amp;#39;; SELECT version(); --` |
|…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-vmw2-qwm8-x84c</guid>
    </item>
  </channel>
</rss>
