CVE-2026-102650

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-11-10. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-118389 (ENISA EUVD) · GHSA-xxrh-5hgg-gj4h (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
65
EG Risk 65/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
29th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 6, 2026

Last Modified

November 12, 2026

Advisory Details (4)

Auto-updated Nov 6, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_pr, github_release.
GitHub release Patch Available

v3.15.2

Patch available: nuxt/content v3.15.2

https://github.com/nuxt/content/releases/tag/v3.15.2
GitHub commit Patch Available

commit 847d523a48e7 (nuxt/content)

Patch available: nuxt/content v3.15.2 (contains commit 847d523a48e7)

https://github.com/nuxt/content/commit/847d523a48e76d861175b325abf0de40dc5864ed
GitHub pull request Patch Available

fix(security): reject SQL function calls in query WHERE clauses

Patch available: nuxt/content v3.15.2 (PR #3819 merged 2026-07-23)

https://github.com/nuxt/content/pull/3819
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Unauthenticated denial of service via SQLite functions in /__nuxt_content/:collection/query · Advisory · nuxt/content · GitHub

https://github.com/nuxt/content/security/advisories/GHSA-xxrh-5hgg-gj4h

Vendor Advisories for CVE-2026-102650(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npm@nuxt/content @ 3.15.2 (fixes >= 3.0.0, < 3.15.2)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@nuxt/content—
  • 3.0.0 up to 3.15.2: fixed in 3.15.2
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 14× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  2. 2026-11-12 22:29 UTCEchelonGraph re-scored
  3. 2026-11-12 22:29 UTCGHSA enrichmentGHSA-xxrh-5hgg-gj4h · GitHub severity HIGH · GitHub CVSS 7.5
  4. 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  5. 2026-11-11 16:37 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  6. 2026-11-10 20:46 UTCEchelonGraph re-scored
  7. 2026-11-10 20:46 UTCGHSA enrichmentGHSA-xxrh-5hgg-gj4h · GitHub severity HIGH · GitHub CVSS 7.5
  8. 2026-11-10 20:33 UTCEchelonGraph re-scored
  9. 2026-11-10 20:33 UTCGHSA enrichmentGHSA-xxrh-5hgg-gj4h · GitHub severity HIGH · GitHub CVSS 7.5
  10. 2026-11-10 20:07 UTCEchelonGraph re-scored
  11. 2026-11-10 20:07 UTCGHSA enrichmentGHSA-xxrh-5hgg-gj4h · GitHub severity HIGH · GitHub CVSS 7.5
  12. 2026-11-10 17:03 UTCEchelonGraph re-scored
  13. 2026-11-10 17:03 UTCGHSA enrichmentGHSA-xxrh-5hgg-gj4h · GitHub severity HIGH · GitHub CVSS 7.5
  14. 2026-11-10 16:41 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  15. 2026-11-09 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  16. 2026-11-08 16:37 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  17. 2026-11-07 16:37 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  18. 2026-11-06 19:04 UTCENISA EUVD ID recordedEUVD-2026-118389 · Source: ENISA EUVD
  19. 2026-11-06 18:27 UTCEchelonGraph re-scored
  20. 2026-11-06 17:48 UTCEchelonGraph re-scoredFirst assessed: 7.5 HIGH
  21. 2026-11-06 17:47 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-102650?
CVE-2026-102650 is a high-severity vulnerability; its CVE record was published on November 6, 2026. 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…
When was the CVE record for CVE-2026-102650 published?
The CVE record for CVE-2026-102650 was published on November 6, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 12, 2026; the record at its source may have been updated since.
Is CVE-2026-102650 actively exploited?
CVE-2026-102650 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (29th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-102650?
CVE-2026-102650 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-102650?
A fix for CVE-2026-102650 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-102650 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-102650

Explore →

Is Your Infrastructure Affected by CVE-2026-102650?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs