How severe is GHSA-vhhq-m2gm-rwc9?

No CVSS score has been assigned to GHSA-vhhq-m2gm-rwc9 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-vhhq-m2gm-rwc9?

GHSA-vhhq-m2gm-rwc9 affects the following packages: @quasar/app-vite (npm). Ecosystems affected: npm.

How do I fix GHSA-vhhq-m2gm-rwc9?

Update @quasar/app-vite to 3.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vhhq-m2gm-rwc9 is resolved across your whole dependency graph.

How do I detect GHSA-vhhq-m2gm-rwc9 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @quasar/app-vite, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-vhhq-m2gm-rwc9 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is GHSA-vhhq-m2gm-rwc9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-vhhq-m2gm-rwc9 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-vhhq-m2gm-rwc9?

GHSA-vhhq-m2gm-rwc9 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 4th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-vhhq-m2gm-rwc9?

GHSA-vhhq-m2gm-rwc9 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-vhhq-m2gm-rwc9 published, and has it been updated?

GHSA-vhhq-m2gm-rwc9 was published on October 7, 2026 and was last updated on October 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Quasar Framework: App Vite SSG page output paths can escape the configured distribution directoryGHSA-vhhq-m2gm-rwc9

Fix: quasarframework/quasar@cdd4dae

GHSA-vhhq-m2gm-rwc9 is a Path Traversal vulnerability in @quasar/app-vite. A fix is available for @quasar/app-vite — see the affected versions and patch details below.

Also known asCVE-2026-106108

Published

Oct 7, 2026

Updated

Oct 7, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-vhhq-m2gm-rwc9.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs4th percentile — riskier than 4% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

5other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@quasar/app-vitenpm

186Kdownloads / week

Description

Summary

During an SSG build, page definitions returned by getSsgPages() can provide custom dir and filename values. The builder joined those values to build.distDir and wrote the generated page without verifying that the final destination remained inside the distribution directory.

Details

A page definition containing parent-directory traversal could cause the build to create a new HTML file outside build.distDir. An existing symlink below the distribution directory could also redirect a generated file or newly created directories outside the output tree.

Quasar application configuration and SSG page definitions are trusted input by default, so this is not normally a remote file-write primitive. The issue becomes relevant when an application derives SSG page definitions from external or otherwise untrusted content, or when build configuration is compromised. Existing files are protected by the SSG renderer's no-overwrite behavior, but new files and directories can be created with the permissions of the build user.

Impact

An attacker able to influence an application's SSG page definitions could create files outside the intended build output directory during quasar build -m ssg.

Remediation

Resolve each page destination against the real build.distDir, reject absolute and parent-traversing paths, reject destinations that resolve to the output root where a file is expected, and verify existing ancestors after resolving symlinks.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@quasar/app-vite`	≥ 3.1.0&&< 3.3.0	3.3.0`npm install @quasar/app-vite@3.3.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @quasar/app-vite, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @quasar/app-vite to 3.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vhhq-m2gm-rwc9 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

## Summary During an SSG build, page definitions returned by `getSsgPages()` can provide custom `dir` and `filename` values. The builder joined those values to `build.distDir` and wrote the generated page without verifying that the final destination remained inside the distribution directory. ## Details A page definition containing parent-directory traversal could cause the build to create a new HTML file outside `build.distDir`. An existing symlink below the distribution directory could also redirect a generated file or newly created directories outside the output tree. Quasar application

O3 Security · Impact-Aware SCA

Is GHSA-vhhq-m2gm-rwc9 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works