CVE Intelligence
Medium File handling

CVE-2026-106108 — Quasar Framework: App Vite SSG page output paths can escape the configured distribution directory

Quasar Framework is a framework for building high-performance Vue.js user interfaces. From 3.1.0 until 3.3.0, @quasar/app-vite SSG page definitions returned by getSsgPages() could supply dir and filename values that were joined to build.distDir without verifying the final destination. Parent traversal or an existing symlink below the distribution directory could create new HTML files or directories outside the output tree with the build user's permissions. Application configuration and SSG page definitions are trusted by default, so exploitation requires a build process that derives them from external or otherwise less-trusted content; existing files remain protected by the renderer's no-overwrite behavior. This issue is fixed in version 3.3.0.

Published Oct 13, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, GitHub Security Advisories, CVE Program (cve.org) e CISA ADP · CNA: GitHub_M

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.2% (30-day exploitation probability)+1
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.15%
ahead of 4% of scored CVEs · Oct 15, 2026
Affects
@quasar
App-vite and 2 more
CVSS base
5.7
Medium · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Npm @quasar/app-vite: fixed in version 3.3.0 — github.com (GitHub Security Advisories)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (@quasar App-vite, Quasarframework Quasar, Npm @quasar/app-vite).
  2. Apply the fixed version or the patch documented under Remediation.
  3. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
  4. Search available logs for exploit probes matching the vulnerability class (file handling), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
@quasar App-vite version >= 3.1.0, < 3.3.0 Vulnerable CVE Program (cve.org) e CISA ADP
Quasarframework Quasar version >= 2.22.0, < 2.23.3 Vulnerable CVE Program (cve.org) e CISA ADP
Npm @quasar/app-vite ≥ 3.1.0 and ≤ 3.2.0 Vulnerable GitHub Security Advisories

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Local
Attack complexity
High
Attack requirements
Present
Privileges required
None
User interaction
Active
Scope
X
Confidentiality (vulnerable system)
None
Integrity (vulnerable system)
High
Availability (vulnerable system)
Low
Confidentiality (subsequent)
None
Integrity (subsequent)
None
Availability (subsequent)
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
5.7 CVSS 4.0 Medium — — security-advisories@github.com via NIST National Vulnerability Database
5.7 CVSS 4.0 Medium — — GitHub_M via CVE Program (cve.org) e CISA ADP
CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:A/VC:N/VI:H/VA:L/SC:N/SI:N/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 (score shown at the top: security-advisories@github.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-22 · Path Traversal

Other CVEs with this weakness →

EPSS over time FIRST

Oct 14, 2026 → Oct 15, 2026 · 2 reading(s) · max 0.15%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
  • Monitor file creation in web directories and paths with traversal sequences (../).
endpoint telemetry (EDR)file integrity (FIM)

Timeline

What happened to this CVE, newest first.

  • 2026
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Affected products added · quasarframework/quasar, @quasar/app-vite
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Fix documented
    Oct 13, 2026 · GitHub Security Advisories
  • Affected products added · npm/@quasar/app-vite
    Oct 13, 2026 · GitHub Security Advisories
  • Record published
    Oct 13, 2026
  • CVSS changed · 5.7
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Received
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVE published
    Oct 13, 2026 · GitHub_M

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 13, 2026 – Oct 13, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

5 on the record

Elsewhere on this site

@quasar
every CVE for this vendor
File handling
same class
CWE-22
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-106107 Quasar Framework: App Vite SSR and SSG nonce attributes are not safely constrained 9d
  • CVE-2026-106109 Quasar Framework: App Vite build cleanup can recursively remove unsafe configured output directories 9d
  • CVE-2026-106106 Quasar Framework: SSR/SSG dev error page discloses the full shell environment and its </script> escape is bypassable 9d
  • CVE-2026-106103 Quasar Framework: Path Traversal / Arbitrary File Write via crafted Icon Genie profile 9d
  • CVE-2026-106105 Quasar Framework: Development TLS private keys are cached with overly permissive filesystem permissions 9d
  • CVE-2026-106104 Quasar Framework: Super-linear regex backtracking on User-Agent lets one request stall a Quasar SSR server 9d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-106108 is "Quasar Framework: App Vite SSG page output paths can escape the configured distribution directory", rated Medium. It affects App-vite (@quasar); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.7 describes technical severity. EPSS 0.15% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.