Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5amended

Nuxt Content: Unauthenticated SQLite Function DoS via Content Query API

CVE-2026-102650GHSA-xxrh-5hgg-gj4h

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@nuxt/content 3.15.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
  • CVE-2026-102650: 0.35% estimated exploitation activity in the next 30 days; percentile 28.95 (FIRST EPSS, 2026-11-10). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary 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.

Details The vulnerability spans three source files: Route registration — `src/module.ts:207-208` The Nuxt Content module registers a public HTTP POST handler for each configured collection at startup: ```ts // src/module.ts:207-208 addServerHandler({…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from osv record GHSA-xxrh-5hgg-gj4h

  2. Revision 1 · created ·

    Published from ghsa record GHSA-xxrh-5hgg-gj4h

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-102650

Advisory: Nuxt Content: Unauthenticated SQLite Function DoS via Content Query API
IDs: CVE-2026-102650, GHSA-xxrh-5hgg-gj4h
Record: https://patchnext.com/advisories/cve-2026-102650 (revision 2, source checked 11 Nov 2026, 06:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @nuxt/content 3.15.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @nuxt/content: affected >= 3.0.0, < 3.15.2; fixed in 3.15.2

## Suggested inspection (read-only)
- `npm ls @nuxt/content --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @nuxt/content.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-xxrh-5hgg-gj4h (GitHub-reviewed advisory GHSA-xxrh-5hgg-gj4h lists affected ranges: npm @nuxt/content >=3.0.0 <3.15.2)
- Verified: https://osv.dev/vulnerability/GHSA-xxrh-5hgg-gj4h (OSV record GHSA-xxrh-5hgg-gj4h lists affected ranges: npm @nuxt/content >=3.0.0 <3.15.2 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…