<?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>Tue, 17 Nov 2026 04:13:12 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-401283</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-401283</link>
      <description>EUVD-2026-401283</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-401283</guid>
    </item>
    <item>
      <title>fkie_cve-2026-102650</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-102650</link>
      <description>&lt;p&gt;Nuxt Content is the file-based CMS for Nuxt applications, powered by Markdown and Vue components. From 3.0.0 until 3.15.2, the unauthenticated POST /__nuxt_content/:collection/query endpoint accepts an attacker-controlled sql field in src/runtime/api/query.post.ts and permits expensive SQLite expressions. Version 3.0.0 performed no query validation; in affected releases using assertSafeQuery in src/runtime/internal/security.ts, the reported validation gap rejects a short list of SQL command keywords in WHERE clauses but permits function calls including randomblob(), zeroblob(), hex(), and length(). The query reaches the synchronous better-sqlite3 sink in src/runtime/internal/database.server.ts, allowing a single remote request to consume substantial CPU and memory while blocking the Node.js event loop and all concurrent request handling. Fully static prerendered deployments that do not expose the server endpoint are not affected. This issue is fixed in version 3.15.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Nuxt Content is the file-based CMS for Nuxt applications, powered by Markdown and Vue components. From 3.0.0 until 3.15.2, the unauthenticated POST /__nuxt_content/:collection/query endpoint accepts an attacker-controlled sql field in src/runtime/api/query.post.ts and permits expensive SQLite expressions. Version 3.0.0 performed no query validation; in affected releases using assertSafeQuery in src/runtime/internal/security.ts, the reported validation gap rejects a short list of SQL command keywords in WHERE clauses but permits function calls including randomblob(), zeroblob(), hex(), and length(). The query reaches the synchronous better-sqlite3 sink in src/runtime/internal/database.server.ts, allowing a single remote request to consume substantial CPU and memory while blocking the Node.js event loop and all concurrent request handling. Fully static prerendered deployments that do not expose the server endpoint are not affected. This issue is fixed in version 3.15.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-102650</guid>
    </item>
    <item>
      <title>GHSA-xxrh-5hgg-gj4h — Nuxt Content: Unauthenticated SQLite Function DoS via Content Query API</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-xxrh-5hgg-gj4h</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @nuxt/content&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The `POST /__nuxt_content/:collection/query` endpoint in `@nuxt/content` accepts an attacker-controlled `sql` field from the HTTP request body and executes it against a local SQLite database after passing it through an insufficient validator (`assertSafeQuery`). The validator only blocks a small set of SQL command keywords and does not reject expensive SQLite built-in functions such as `randomblob()`, `zeroblob()`, `hex()`, or `length()`. An unauthenticated remote attacker can craft a single request that forces SQLite to allocate hundreds of megabytes of memory and perform CPU-intensive work, causing server-wide denial of service. This endpoint is enabled by default for every collection and requires no authentication.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The vulnerability spans three source files:&lt;/p&gt;
&lt;p&gt;**Route registration — `src/module.ts:207-208`**&lt;/p&gt;
&lt;p&gt;The Nuxt Content module registers a public HTTP POST handler for each configured collection at startup:&lt;/p&gt;
&lt;p&gt;```ts
// src/module.ts:207-208
addServerHandler({
  route: `/__nuxt_content/${collection.name}/query`,
  handler: resolver.resolve(&amp;#39;./runtime/api/query.post&amp;#39;),
})
```&lt;/p&gt;
&lt;p&gt;No authentication middleware is attached; the route is reachable by any client.&lt;/p&gt;
&lt;p&gt;**Source (attacker input) — `src/runtime/api/query.post.ts:7-9`**&lt;/p&gt;
&lt;p&gt;```ts
// src/runtime/api/query.post.ts
const { sql } = await readBody(event)          // line 8  — attacker-controlled
assertSafeQuery(sql, collection)               // line 11 — insufficient validation
return loadDatabaseAdapte…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @nuxt/content&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The `POST /__nuxt_content/:collection/query` endpoint in `@nuxt/content` accepts an attacker-controlled `sql` field from the HTTP request body and executes it against a local SQLite database after passing it through an insufficient validator (`assertSafeQuery`). The validator only blocks a small set of SQL command keywords and does not reject expensive SQLite built-in functions such as `randomblob()`, `zeroblob()`, `hex()`, or `length()`. An unauthenticated remote attacker can craft a single request that forces SQLite to allocate hundreds of megabytes of memory and perform CPU-intensive work, causing server-wide denial of service. This endpoint is enabled by default for every collection and requires no authentication.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The vulnerability spans three source files:&lt;/p&gt;
&lt;p&gt;**Route registration — `src/module.ts:207-208`**&lt;/p&gt;
&lt;p&gt;The Nuxt Content module registers a public HTTP POST handler for each configured collection at startup:&lt;/p&gt;
&lt;p&gt;```ts
// src/module.ts:207-208
addServerHandler({
  route: `/__nuxt_content/${collection.name}/query`,
  handler: resolver.resolve(&amp;#39;./runtime/api/query.post&amp;#39;),
})
```&lt;/p&gt;
&lt;p&gt;No authentication middleware is attached; the route is reachable by any client.&lt;/p&gt;
&lt;p&gt;**Source (attacker input) — `src/runtime/api/query.post.ts:7-9`**&lt;/p&gt;
&lt;p&gt;```ts
// src/runtime/api/query.post.ts
const { sql } = await readBody(event)          // line 8  — attacker-controlled
assertSafeQuery(sql, collection)               // line 11 — insufficient validation
return loadDatabaseAdapte…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-xxrh-5hgg-gj4h</guid>
    </item>
  </channel>
</rss>
