Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 4.1amended

Quasar Framework: App Vite build cleanup can recursively remove unsafe configured output directories

CVE-2026-106109GHSA-q9mq-245r-4g93

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@quasar/app-vite 3.3.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
4.1 · CVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:A/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-106109: 0.13% estimated exploitation activity in the next 30 days; percentile 2.26 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary @quasar/app-vite recursively removes build.distDir before producing build artifacts. The configured path was made absolute, but it was not checked before removal. A configuration mistake could therefore target the project root, user home directory, a filesystem root, or another directory outside the project. Details The build command and mode builders passed the resolved output directory directly to fs-extra recursive removal. Existing symlink ancestors were not resolved before deletion either, so a path that appeared to be inside the project could operate on a directory outside it. quasar.config is trusted application code, and no attacker-controlled input reaches build.distDir by default. This issue is primarily destructive-build safety hardening. It can become a security boundary when build configuration is generated or influenced by less-trusted automation. Impact Running a normal Quasar build with an unsafe build.distDir can delete data accessible to the build user…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-q9mq-245r-4g93

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GHSA-q9mq-245r-4g93

  4. Revision 1 · created ·

    Published from ghsa record GHSA-q9mq-245r-4g93

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-106109

Advisory: Quasar Framework: App Vite build cleanup can recursively remove unsafe configured output directories
IDs: CVE-2026-106109, GHSA-q9mq-245r-4g93
Record: https://patchnext.com/advisories/cve-2026-106109 (revision 4, source checked 26 Oct 2026, 13:06 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @quasar/app-vite 3.3.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @quasar/app-vite: affected >= 1.0.0, <= 3.2.0; fixed in 3.3.0

## Suggested inspection (read-only)
- `npm ls @quasar/app-vite --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @quasar/app-vite.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-q9mq-245r-4g93 (GitHub-reviewed advisory GHSA-q9mq-245r-4g93 lists affected ranges: npm @quasar/app-vite >=1.0.0 <=3.2.0)
- Verified: https://osv.dev/vulnerability/GHSA-q9mq-245r-4g93 (OSV record GHSA-q9mq-245r-4g93 lists affected ranges: npm @quasar/app-vite >=1.0.0 <3.3.0 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…