Nuxt Content: Unauthenticated SQLite Function DoS via Content Query API
Affects Nuxt Content from 3.0.0 before 3.15.2 when the app uses the default SQLite/D1 adapter and exposes the server query endpoint. Fixed in 3.15.2.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.15.2
- Who is exposed
- Default setups
Do first: Check every install: default setups are affected.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 30/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Default setups
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Nuxt Content, the file-based CMS for Nuxt applications, has a flaw that lets a remote attacker, without logging in, send one crafted SQL query that consumes substantial CPU and memory and blocks the Node.js event loop, halting all concurrent requests. Fully static prerendered deployments that don't expose the server endpoint are not affected.
Read the original description
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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure22/25Default setups, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
What to do
Check every install: default setups are affected.
Upgrade to a fixed version: 3.15.2.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- nuxt content
From 3.0.0 · fixed in 3.15.2
Evidence 4
- Advisory
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-102650
Is CVE-2026-102650 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A single crafted request to the server query endpoint can use substantial CPU and memory and block the Node.js event loop. This stalls all concurrent request handling on the server.Source: github.com
Which versions are affected by CVE-2026-102650?
content: from 3.0.0 before 3.15.2.Source: cve.now feed data
Am I affected, and how do I check?
Nuxt Content versions from 3.0.0 before 3.15.2 are affected when the app uses the default SQLite/D1 adapter and exposes the server query endpoint. Check the installed version in the package manifest or lockfile, and check whether the default SQLite/D1 adapter is in use.Source: github.com
How do I fix CVE-2026-102650?
Upgrade Nuxt Content to 3.15.2 or later.Source: github.com