CVE-2026-114131

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreHIGH confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-107414 (ENISA EUVD) · GHSA-6gq8-jgmh-3ffp (GitHub Security Advisories)Source: ENISA EUVD

6.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Nuxt is an open-source web development framework for Vue.js. From 3.11.0 until 3.21.4 and 4.4.4, Nuxt compares route-rule keys with the raw request path while route resolution decodes dynamic and catch-all parameters, allowing a percent-encoded segment to resolve to a protected page without matching the routeRules entry intended for that path. As a result, appMiddleware can be skipped during server rendering and an unauthenticated requester can receive the gated page and its SSR data. The same mismatch affects app-manifest rules including redirect, appLayout, ssr, prerender, and payload flags derived from cache, isr, and swr. This vulnerability is fixed in 4.4.4 and 3.21.4.

CVSS v3
6.5
EG Score
6.5MEDIUMhigh confidence
EG Risk
44
EG Risk 44/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)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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 none (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
30th
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 (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-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-10-31). 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 none (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

October 21, 2026

Last Modified

October 30, 2026

Advisory Details (5)

Auto-updated Oct 22, 2026
Patch available. Sources: github, github_commit, github_release.
GitHub advisoryMentions a patch (unverified)

Route rules are matched against the raw request path, so a percent-encoded segment can bypass `appMiddleware` on dynamic and catch-all routes · Advisory · nuxt/nuxt · GitHub

https://github.com/nuxt/nuxt/security/advisories/GHSA-6gq8-jgmh-3ffp
GitHub release Patch Available

Release v4.5.2 (nuxt/nuxt)

Patch available: nuxt/nuxt v4.5.2

https://github.com/nuxt/nuxt/releases/tag/v4.5.2
GitHub release Patch Available

Release v3.21.11 (nuxt/nuxt)

Patch available: nuxt/nuxt v3.21.11

https://github.com/nuxt/nuxt/releases/tag/v3.21.11
GitHub commit

commit 9123ed850c46 (nuxt/nuxt)

Fix landed in nuxt/nuxt commit 9123ed850c46 — awaiting tagged release

https://github.com/nuxt/nuxt/commit/9123ed850c468a7424a868c20d0d49a5507d32e5
GitHub commit

commit 81f86ac5ee82 (nuxt/nuxt)

Fix landed in nuxt/nuxt commit 81f86ac5ee82 — awaiting tagged release

https://github.com/nuxt/nuxt/commit/81f86ac5ee82bb1a9b887e59f3bc84624d711497

Vendor Advisories for CVE-2026-114131(1)

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmnuxt @ 4.4.4 (fixes >= 4.0.0, < 4.4.4)—ghsa
npmnuxt @ 3.21.4 (fixes >= 3.11.0, < 3.21.4)—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—
  • 4.0.0 up to 4.4.4: fixed in 4.4.4
  • 3.11.0 up to 3.21.4: fixed in 3.21.4
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 21× 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 it from the CNA feed. 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). Most recent first.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  2. 2026-11-01 07:59 UTCGHSA enrichmentGHSA-6gq8-jgmh-3ffp · GitHub severity MODERATE · GitHub CVSS 6.5
  3. 2026-11-01 07:59 UTCEG score recompute
  4. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  5. 2026-10-30 18:27 UTCEG score recompute
  6. 2026-10-30 17:56 UTCEG score recompute
  7. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  8. 2026-10-30 02:55 UTCOSV refresh
  9. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  10. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  11. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  12. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  13. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  14. 2026-10-25 14:50 UTCEG score recompute
  15. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  16. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  17. 2026-10-22 17:09 UTCEG score recompute
  18. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  19. 2026-10-21 18:26 UTCEG score recompute
  20. 2026-10-21 17:46 UTCEG score recomputeFirst assessed: 6.5 MEDIUM
  21. 2026-10-21 17:45 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-114131?
CVE-2026-114131 is a medium-severity vulnerability; its CVE record was published on October 21, 2026. Nuxt is an open-source web development framework for Vue.js. From 3.11.0 until 3.21.4 and 4.4.4, Nuxt compares route-rule keys with the raw request path while route resolution decodes dynamic and catch-all parameters, allowing a percent-encoded segment to resolve to a protected page without…
When was the CVE record for CVE-2026-114131 published?
The CVE record for CVE-2026-114131 was published on October 21, 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 October 30, 2026; the record at its source may have been updated since.
Is CVE-2026-114131 actively exploited?
CVE-2026-114131 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (30th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-114131?
CVE-2026-114131 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-114131?
A fix for CVE-2026-114131 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-114131 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-114131

Explore →

Is Your Infrastructure Affected by CVE-2026-114131?

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