Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-106106

Cross-Site Scripting (XSS) in @quasar/render-ssr-error (CVE-2026-106106)

Summary

Cross-site scripting in @quasar/render-ssr-error (CVE-2026-106106). Risk of unauthorized operations or information disclosure. Exploitable via process.env. Mitigation: upgrade to 2.2.4 or later.

Original description

The description as published by the source.

Summary

The error page that Quasar CLI shows when an SSR or SSG render throws in development serializes every variable in process.env, every request header and every cookie into the HTTP response, and the dev server binds 0.0.0.0 by default. Any host that can reach the port therefore gets the developer's cloud keys, registry tokens and database URLs from a single unauthenticated GET. The same page embeds that data inside a element behind a `replaceAll('', ...)` guard that is ASCII-case-sensitive and requires a literal `>`, so, and all escape the element and give script execution in the dev server's origin.

Details

renderSSRError() builds the page by splicing a JSON blob into a prebuilt bundle (utils/render-ssr-error/src/index.js):

errorHtml:
  before +
  JSON.stringify(data).replaceAll('', String.raw`<\/script>`) +
  after

before and after are the two halves of the compiled error-page UI, split inside a `` element, so data is emitted as a JS object literal in raw script text. The data itself comes from utils/render-ssr-error/src/env.js:

function getEnvironmentVariablesData () {
  return Object.keys(process.env).reduce((acc, name) => {
    acc[ name ] = process.env[ name ]
    return acc
  }, {})
}

export function getEnv (req) {
  return {
    Request: getRequestData(req),
    Headers: getHeadersData(req),
    Cookies: getCookiesData(req),
    'Shell environment variables': getEnvironmentVariablesData()
  }
}

The…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-106106 has been found in @quasar/render-ssr-error.
Attackers can target a specific entry point like process.env over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade @quasar/render-ssr-error to 2.2.4 or later.
If unsure, ask your IT team or search "@quasar/render-ssr-error CVE-2026-106106" on the vendor's site.

CVE-2026-106106 (@quasar/render-ssr-error) — CWE-79
Attack surface: process.env / before / after / data
Patched: 2.2.4 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Cross-site scripting (XSS) (CWE-79) exists in @quasar/render-ssr-error. Attackers reach the vulnerable code path via process.env.

📍 Affected scope

Check the vendor advisory for the affected versions of @quasar/render-ssr-error. Attack surface: process.env / before / after / data.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.2.4.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@quasar/render-ssr-error' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r '@quasar/render-ssr-error' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で @quasar/render-ssr-error を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade @quasar/render-ssr-error to 2.2.4

    ステージング環境で 2.2.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm @quasar/render-ssr-error
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.4"}]}]
npm @quasar/app-vite
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.3.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details