CVE-2026-106106: Quasar Framework: SSR/SSG dev error page discloses the full shell environment and its </script> escape is bypassable
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.27% (FIRST EPSS).
- Someone on the same network segment can trigger it. No account or password is required. Special conditions such as timing or configuration are required.
- Fixed version: @quasar/app-vite (npm) 3.3.0; @quasar/render-ssr-error (npm) 2.2.4.
Low priority for now. Upgrade to @quasar/app-vite (npm) 3.3.0; @quasar/render-ssr-error (npm) 2.2.4 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 6, 2026
- Updated
- Oct 6, 2026
- EPSS
- 0.2% · 20th percentile
- CWE
- CWE-79
Report tools
Action score
28
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 7.1
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:A/AC:H/AT:P/PR:N/UI:P/VC:H/VI:L/VA:N/SC:H/SI:H/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Limit the impact of XSSCheck security headers
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Limit the impact of XSS
This is a cross-site scripting (XSS) vulnerability. A well-configured Content-Security-Policy doesn't fix it, but greatly reduces its impact. Check your site's CSP and other security headers for free.
Check security headersVersions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
@quasar app-vite
- < 3.3.0affected
@quasar render-ssr-error
- < 2.2.4affected
quasarframework quasar
- < 2.23.3affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| npm | @quasar/app-vite | before 3.3.0 | 3.3.0 |
| npm | @quasar/render-ssr-error | before 2.2.4 | 2.2.4 |
Same product
quasarframework: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-106102Quasar Framework: Stored/Reflected XSS via unescaped SSR meta tag rendering in getHead()40Plan
- CVE-2026-106104Quasar Framework: Super-linear regex backtracking on User-Agent lets one request stall a Quasar SSR server34Monitor
- CVE-2026-106107Quasar Framework: App Vite SSR and SSG nonce attributes are not safely constrained33Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-106103Oct 6, 2026 · Quasar Framework: Path Traversal / Arbitrary File Write via crafted Icon Genie profile28Monitor
- ← EarlierCVE-2026-106105Oct 6, 2026 · Quasar Framework: Development TLS private keys are cached with overly permissive filesystem permissions33Monitor
- Later →CVE-2026-106109Oct 6, 2026 · Quasar Framework: App Vite build cleanup can recursively remove unsafe configured output directories16Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| npm:@quasar/app-vite | 3.3.0 | Package registry (OSV) |
| npm:@quasar/render-ssr-error | 2.2.4 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recorded+1 d
- TodayNov 14, 2026+39 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-1061020 days apartQuasar Framework: Stored/Reflected XSS via unescaped SSR meta tag rendering in getHead()40Plan
- CVE-2026-1061070 days apartQuasar Framework: App Vite SSR and SSG nonce attributes are not safely constrained33Monitor
Not on record for this CVE: researcher credit · public bounty program.
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Adjacent
- Attack complexity
- High
- Privileges required
- None
- User interaction
- P
- Scope
- X
Weakness class (CWE)
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')CVSS vector
CVSS:4.0/AV:A/AC:H/AT:P/PR:N/UI:P/VC:H/VI:L/VA:N/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Root cause
User content is inserted into the page as HTML. The browser interprets the content as code rather than data.
The bug in code
The whole CWE-79 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
commentEl.innerHTML = comment.body;Fixed
commentEl.textContent = comment.body;Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
- SSVC exploitation— → poc
- Exploit maturity— → none
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.