CVE-2026-106106

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (20th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-93571 (ENISA EUVD) · GHSA-r5mf-4r5x-q78f (GitHub Security Advisories)Source: ENISA EUVD

7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (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.3%CVSS: 7.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Quasar Framework is a framework for building high-performance Vue.js user interfaces. Prior to @quasar/render-ssr-error 2.2.4 and @quasar/app-vite 3.3.0, renderSSRError() in utils/render-ssr-error/src/index.js used diagnostic data from utils/render-ssr-error/src/env.js to serialize process.env, request headers, and cookies into the HTTP page returned by serve.devError(), while the development server listened on all interfaces by default. Any network-adjacent client that reaches an SSR or SSG render failure through this development-only error path can obtain shell environment secrets. The renderer escaped only one exact lowercase script closing-tag spelling, so case variants and valid closing-tag delimiter variants in reflected diagnostic data could terminate the script element and inject markup; executing the injected code in a developer browser additionally requires the payload to accompany that developer's request. This issue is fixed in @quasar/render-ssr-error 2.2.4 and @quasar/app-vite 3.3.0.

CVSS
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
48
EG Risk 48/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)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 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.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.3%
EPSS %ILE
20th
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.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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 6, 2026

Last Modified

October 6, 2026

Advisory Details (2)

Auto-updated Oct 6, 2026
Patch available. Sources: github, github_commit.
GitHub commit Patch Available

commit 61c2bd8a6077 (quasarframework/quasar)

Patch available: quasarframework/quasar quasar-v2.26.0 (contains commit 61c2bd8a6077)

https://github.com/quasarframework/quasar/commit/61c2bd8a607785fdade72cce20e8faf1de7eee15
GitHub advisoryMentions a patch (unverified)

SSR/SSG dev error page discloses the full shell environment and its </script> escape is bypassable · Advisory · quasarframework/quasar · GitHub

https://github.com/quasarframework/quasar/security/advisories/GHSA-r5mf-4r5x-q78f

Vendor Advisories for CVE-2026-106106(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
npm@quasar/app-vite @ 3.3.0 (fixes <= 3.2.0)—ghsa
npm@quasar/render-ssr-error @ 2.2.4 (fixes <= 2.2.3)—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

(2 across 1 ecosystem)
npm(2)
PackageVulnerable rangeFix by version rangeDependents
@quasar/app-vite—
  • every version up to 3.3.0: fixed in 3.3.0
—
@quasar/render-ssr-error—
  • every version up to 2.2.4: fixed in 2.2.4
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 34× 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 → 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.3% · 20th percentile
  2. 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  3. 2026-11-11 16:37 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  4. 2026-11-11 03:25 UTCEchelonGraph re-scored
  5. 2026-11-11 03:25 UTCGHSA enrichmentGHSA-r5mf-4r5x-q78f · GitHub severity HIGH
  6. 2026-11-10 16:41 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  7. 2026-11-10 05:45 UTCEchelonGraph re-scored
  8. 2026-11-10 05:45 UTCGHSA enrichmentGHSA-r5mf-4r5x-q78f · GitHub severity HIGH
  9. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  10. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  11. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  12. 2026-11-06 16:35 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  13. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  14. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  15. 2026-11-03 19:52 UTCEchelonGraph re-scored
  16. 2026-11-03 19:52 UTCGHSA enrichmentGHSA-r5mf-4r5x-q78f · GitHub severity HIGH
  17. 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  18. 2026-11-03 05:29 UTCEchelonGraph re-scored
  19. 2026-11-03 05:29 UTCGHSA enrichmentGHSA-r5mf-4r5x-q78f · GitHub severity HIGH
  20. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  21. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-r5mf-4r5x-q78f · GitHub severity HIGH
  22. 2026-11-01 08:00 UTCEchelonGraph re-scored
  23. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  24. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  25. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
Show 40 more
  1. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  2. 2026-10-27 19:36 UTCEchelonGraph re-scored
  3. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  4. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  5. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  6. 2026-10-25 14:55 UTCEchelonGraph re-scored
  7. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  8. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  9. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  10. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  11. 2026-10-20 19:12 UTCEchelonGraph re-scored
  12. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  13. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  14. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  15. 2026-10-18 05:08 UTCEchelonGraph re-scored
  16. 2026-10-17 19:31 UTCEchelonGraph re-scored
  17. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  18. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  19. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  20. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  21. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  22. 2026-10-12 16:39 UTCEchelonGraph re-scored
  23. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  24. 2026-10-11 20:14 UTCEchelonGraph re-scored
  25. 2026-10-11 18:27 UTCEchelonGraph re-scored
  26. 2026-10-11 15:00 UTCEchelonGraph re-scored
  27. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  28. 2026-10-11 12:52 UTCEchelonGraph re-scored
  29. 2026-10-11 01:37 UTCEchelonGraph re-scored
  30. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  31. 2026-10-10 03:05 UTCEchelonGraph re-scored
  32. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  33. 2026-10-08 17:19 UTCEchelonGraph re-scored
  34. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  35. 2026-10-08 06:04 UTCEchelonGraph re-scored
  36. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  37. 2026-10-06 19:37 UTCEchelonGraph re-scored
  38. 2026-10-06 18:31 UTCEchelonGraph re-scored
  39. 2026-10-06 17:37 UTCEchelonGraph re-scoredFirst assessed: 7.1 HIGH
  40. 2026-10-06 17:37 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-106106?
CVE-2026-106106 is a high-severity vulnerability; its CVE record was published on October 6, 2026. Quasar Framework is a framework for building high-performance Vue.js user interfaces. Prior to @quasar/render-ssr-error 2.2.4 and @quasar/app-vite 3.3.0, renderSSRError() in utils/render-ssr-error/src/index.js used diagnostic data from utils/render-ssr-error/src/env.js to serialize process.env,…
When was the CVE record for CVE-2026-106106 published?
The CVE record for CVE-2026-106106 was published on October 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 October 6, 2026; the record at its source may have been updated since.
Is CVE-2026-106106 actively exploited?
CVE-2026-106106 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-106106?
CVE-2026-106106 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-106106?
A fix for CVE-2026-106106 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-106106 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-106106

Explore →

Is Your Infrastructure Affected by CVE-2026-106106?

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

Book a Demo →Browse All CVEs