<?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://cve.radiocsirt.org</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, 05 Oct 2026 21:22:49 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-270967</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-270967</link>
      <description>EUVD-2026-270967</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-270967</guid>
    </item>
    <item>
      <title>fkie_cve-2026-25591</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-25591</link>
      <description>&lt;p&gt;New API is a large language mode (LLM) gateway and artificial intelligence (AI) asset management system. Prior to version 0.10.8-alpha.10, a SQL LIKE wildcard injection vulnerability in the `/api/token/search` endpoint allows authenticated users to cause denial of service through resource exhaustion by crafting malicious search patterns. The token search endpoint accepts user-supplied `keyword` and `token` parameters that are directly concatenated into SQL LIKE clauses without escaping wildcard characters (`%`, `_`). This allows attackers to inject patterns that trigger expensive database queries. Version 0.10.8-alpha.10 contains a patch.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;New API is a large language mode (LLM) gateway and artificial intelligence (AI) asset management system. Prior to version 0.10.8-alpha.10, a SQL LIKE wildcard injection vulnerability in the `/api/token/search` endpoint allows authenticated users to cause denial of service through resource exhaustion by crafting malicious search patterns. The token search endpoint accepts user-supplied `keyword` and `token` parameters that are directly concatenated into SQL LIKE clauses without escaping wildcard characters (`%`, `_`). This allows attackers to inject patterns that trigger expensive database queries. Version 0.10.8-alpha.10 contains a patch.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-25591</guid>
    </item>
    <item>
      <title>GHSA-w6x6-9fp7-fqm4 — New API has an SQL LIKE Wildcard Injection DoS via Token Search</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-w6x6-9fp7-fqm4</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/QuantumNous/new-api&lt;/p&gt;
&lt;p&gt;### Summary
A SQL LIKE wildcard injection vulnerability in the `/api/token/search` endpoint allows authenticated users to cause Denial of Service through resource exhaustion by crafting malicious search patterns.&lt;/p&gt;
&lt;p&gt;### Details
The token search endpoint accepts user-supplied `keyword` and `token` parameters that are directly concatenated into SQL LIKE clauses without escaping wildcard characters (`%`, `_`). This allows attackers to inject patterns that trigger expensive database queries.&lt;/p&gt;
&lt;p&gt;### Vulnerable Code
File: `model/token.go:70`
```go
err = DB.Where(&amp;#34;user_id = ?&amp;#34;, userId).
       Where(&amp;#34;name LIKE ?&amp;#34;, &amp;#34;%&amp;#34;+keyword+&amp;#34;%&amp;#34;).     // No wildcard escaping
       Where(commonKeyCol+&amp;#34; LIKE ?&amp;#34;, &amp;#34;%&amp;#34;+token+&amp;#34;%&amp;#34;).
       Find(&amp;amp;tokens).Error
```&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;After creating over 2 million tokens, creating millions token entries is not difficult, because the rate limiting only applies to IP addresses, so multiple IP addresses can share one session, allowing for the creation of an unlimited number of tokens in batches.&lt;/p&gt;
&lt;p&gt;&amp;lt;img width=&amp;#34;1636&amp;#34; height=&amp;#34;659&amp;#34; alt=&amp;#34;image&amp;#34; src=&amp;#34;https://github.com/user-attachments/assets/55e63dcd-884d-41bc-9bea-4300ba1b50c6&amp;#34; /&amp;gt;&lt;/p&gt;
&lt;p&gt;These data are not all loaded at once under normal circumstances, as shown in the image, and are displayed correctly. But if a request like this is submitted:&lt;/p&gt;
&lt;p&gt;```bash
# A single request causes PostgreSQL to unconditionally retrieve all tokens belonging to that user. These requests buffer will all go into the buffer zone, causing an overflow and pre…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/QuantumNous/new-api&lt;/p&gt;
&lt;p&gt;### Summary
A SQL LIKE wildcard injection vulnerability in the `/api/token/search` endpoint allows authenticated users to cause Denial of Service through resource exhaustion by crafting malicious search patterns.&lt;/p&gt;
&lt;p&gt;### Details
The token search endpoint accepts user-supplied `keyword` and `token` parameters that are directly concatenated into SQL LIKE clauses without escaping wildcard characters (`%`, `_`). This allows attackers to inject patterns that trigger expensive database queries.&lt;/p&gt;
&lt;p&gt;### Vulnerable Code
File: `model/token.go:70`
```go
err = DB.Where(&amp;#34;user_id = ?&amp;#34;, userId).
       Where(&amp;#34;name LIKE ?&amp;#34;, &amp;#34;%&amp;#34;+keyword+&amp;#34;%&amp;#34;).     // No wildcard escaping
       Where(commonKeyCol+&amp;#34; LIKE ?&amp;#34;, &amp;#34;%&amp;#34;+token+&amp;#34;%&amp;#34;).
       Find(&amp;amp;tokens).Error
```&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;After creating over 2 million tokens, creating millions token entries is not difficult, because the rate limiting only applies to IP addresses, so multiple IP addresses can share one session, allowing for the creation of an unlimited number of tokens in batches.&lt;/p&gt;
&lt;p&gt;&amp;lt;img width=&amp;#34;1636&amp;#34; height=&amp;#34;659&amp;#34; alt=&amp;#34;image&amp;#34; src=&amp;#34;https://github.com/user-attachments/assets/55e63dcd-884d-41bc-9bea-4300ba1b50c6&amp;#34; /&amp;gt;&lt;/p&gt;
&lt;p&gt;These data are not all loaded at once under normal circumstances, as shown in the image, and are displayed correctly. But if a request like this is submitted:&lt;/p&gt;
&lt;p&gt;```bash
# A single request causes PostgreSQL to unconditionally retrieve all tokens belonging to that user. These requests buffer will all go into the buffer zone, causing an overflow and pre…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-w6x6-9fp7-fqm4</guid>
    </item>
  </channel>
</rss>
