Skip to content
Heist/ feed
Back to feed
MediumFix available

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

Type: advisorySources: OSV

## 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 before compilation begins. ## Remediation Validate the effective deletion target before every artifact cleanup. Always reject filesystem roots, the user home directory and the project root; resolve existing symlink ancestors; require an explicit `build.allowOutsideProjectDistDir` opt-in for external output directories; and log the exact resolved target before removal.

Products
@quasar/app-vite
Affected versions
Not specified
Fixed versions
3.3.0
CVEs
CVE-2026-106109
Confirmed fixed CVEs
Not specified
Updated in this feed
28 Oct 2026, 05:12 UTC · Revision 1

Source evidence

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

core-osv · Original source

Published 7 Oct 2026, 16:14 UTC

## 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 before compilation begins. ## Remediation Validate the effective deletion target before every artifact cleanup. Always reject filesystem roots, the user home directory and the project root; resolve existing symlink ancestors; require an explicit `build.allowOutsideProjectDistDir` opt-in for external output directories; and log the exact resolved target before removal.

osv:GHSA-q9mq-245r-4g93

@quasar/app-vite

Fixed versions: 3.3.0

Complete source record
{
  "id": "d757e73d793c0a2c0033a146b72c718cf513fa291ffd87a77494d1c0b70695ee",
  "url": "https://osv.dev/vulnerability/GHSA-q9mq-245r-4g93",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "Quasar Framework: App Vite build cleanup can recursively remove unsafe configured output directories",
    "summary": "## 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 before compilation begins. ## Remediation Validate the effective deletion target before every artifact cleanup. Always reject filesystem roots, the user home directory and the project root; resolve existing symlink ancestors; require an explicit `build.allowOutsideProjectDistDir` opt-in for external output directories; and log the exact resolved target before removal.",
    "evidence": "osv:GHSA-q9mq-245r-4g93",
    "products": [
      {
        "name": {
          "value": "@quasar/app-vite",
          "evidence": "/affected/0/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "3.3.0",
            "evidence": "/affected/0/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "medium",
    "structured": {
      "id": "GHSA-q9mq-245r-4g93",
      "aliases": [
        "CVE-2026-106109",
        "GHSA-q9mq-245r-4g93"
      ],
      "metrics": [
        {
          "type": "CVSS_V4",
          "score": "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"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "type": "SEMVER",
              "events": [
                {
                  "introduced": "1.0.0"
                },
                {
                  "fixed": "3.3.0"
                }
              ]
            }
          ],
          "package": {
            "name": "@quasar/app-vite",
            "purl": "pkg:npm/%40quasar/app-vite",
            "ecosystem": "npm"
          },
          "database_specific": {
            "source": "https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/10/GHSA-q9mq-245r-4g93/GHSA-q9mq-245r-4g93.json",
            "last_known_affected_version_range": "<= 3.2.0"
          }
        }
      ],
      "modified": "2026-10-07T16:30:06.349887482Z",
      "provider": "osv",
      "references": [
        "https://github.com/quasarframework/quasar/security/advisories/GHSA-q9mq-245r-4g93",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-106109",
        "https://github.com/quasarframework/quasar/commit/6c009734b406e246a0855ed060e3a822de8aecc1",
        "https://github.com/quasarframework/quasar",
        "https://github.com/quasarframework/quasar/releases/tag/@quasar/app-vite-v3.3.0"
      ],
      "provider_metadata": {
        "cwe_ids": [
          "CWE-22",
          "CWE-73"
        ],
        "severity": "MODERATE",
        "github_reviewed": true,
        "nvd_published_at": "2026-10-06T18:16:52Z",
        "github_reviewed_at": "2026-10-07T16:14:35Z"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-106109",
        "evidence": "/aliases"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 95169,
  "published_at": "2026-10-07T16:14:35+00:00"
}