# Quasar Framework: App Vite SSG page output paths can escape the configured distribution directory

Advisory record · `GHSA-vhhq-m2gm-rwc9`

- **Identifiers:** `GHSA-vhhq-m2gm-rwc9` · `CVE-2026-106108`
- **State:** Confirmed
- **Severity:** CVSS 5.7 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 7 Oct 2026
- **Updated:** 7 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 7 Oct 2026, 16:14 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `@quasar/app-vite` (npm): affected `>=3.1.0, <3.3.0`; fixed in `3.3.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Quasar's @quasar/app-vite package, versions 3.1.0 up to but not including 3.3.0, can let SSG page output paths escape the configured build.distDir directory when custom dir or filename values are used. An attacker would need to influence an app's SSG page definitions, such as by deriving them from untrusted content or compromising the build configuration, and could then create new files and directories outside the build output during quasar build -m ssg. Upgrade @quasar/app-vite to version 3.3.0 or later.

Written 31 Oct 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.7 Medium, CVSS 4.0: `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`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0014, the 3rd percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 13:33 UTC: First seen by agentprime
- 31 Oct 2026, 13:33 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-vhhq-m2gm-rwc9)

## Sources

- [GitHub Advisory Database: GHSA-vhhq-m2gm-rwc9](https://github.com/advisories/GHSA-vhhq-m2gm-rwc9)
- [OSV: GHSA-vhhq-m2gm-rwc9](https://osv.dev/vulnerability/GHSA-vhhq-m2gm-rwc9)
- <https://github.com/quasarframework/quasar/security/advisories/GHSA-vhhq-m2gm-rwc9>
- <https://github.com/quasarframework/quasar/commit/cdd4daeec839215540221122763c7a17cd478abc>
- <https://github.com/quasarframework/quasar>
- <https://github.com/quasarframework/quasar/releases/tag/@quasar/app-vite-v3.1.0>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-vhhq-m2gm-rwc9>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-vhhq-m2gm-rwc9/>. Everything for agents: <https://agentprime.io/llms.txt>.