Allocation of Resources Without Limits or Throttling Affecting @nuxt/content package, versions >=3.0.0 <3.15.2
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Allocation of Resources Without Limits or Throttling vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JS-NUXTCONTENT-22400858
- published10 Nov 2026
- disclosed6 Nov 2026
- creditEQSTLab, MinKyeong Kim, Pig-Tail, maru1009
Introduced: 6 Nov 2026
NewCVE-2026-102650 (opens in a new tab)How to fix?
Upgrade @nuxt/content to version 3.15.2 or higher.
Overview
@nuxt/content is a Write your content inside your Nuxt app
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via the assertSafeQuery function in src/runtime/internal/security.ts, which validates the attacker-controlled sql field accepted by the unauthenticated POST /__nuxt_content/:collection/query endpoint in src/runtime/api/query.post.ts. The validator blocks only a short denylist of SQL command keywords and does not reject SQLite built-in functions such as randomblob(), zeroblob(), hex(), and length(). A remote attacker can submit a single request whose WHERE clause chains these functions to force SQLite to allocate hundreds of megabytes of memory and perform CPU-intensive work, which blocks the synchronous better-sqlite3 sink in src/runtime/internal/database.server.ts and stalls the entire Node.js event loop for the duration of the query.
Note: Fully static prerendered deployments that do not expose the server endpoint are not affected.
Workaround
If upgrading is not possible, block or restrict access to POST /__nuxt_content/*/query at the proxy or WAF level, or prerender the site so the endpoint is not deployed.