PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-106109 Quasar Framework CVE debrief

The CVE record was published on 2026-10-07T16:14:35.000Z and has not been modified since then. The NVD entry is currently null. This vulnerability affects Quasar Framework applications using @quasar/app-vite, potentially leading to data loss if the configured build.distDir targets sensitive directories. Defenders should assess exposure and verify build configurations to prevent data loss. The vulnerability is primarily destructive-build safety hardening, which can become a security boundary when build configuration is generated or influenced by less-trusted automation.

Vendor
Quasar Framework
Product
@quasar/app-vite
CVSS
MEDIUM 4.1
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-07
Original CVE updated
2026-10-07
Advisory published
2026-10-07
Advisory updated
2026-10-07

Who should care

Defenders responsible for Quasar Framework applications using @quasar/app-vite should assess exposure and verify build configurations to prevent data loss. This includes operators, platform administrators, vulnerability management teams, and security teams who need to validate effective deletion targets before artifact cleanup to prevent data loss.

Why it matters

Defenders should prioritize validating deletion targets to prevent data loss due to a vulnerability in @quasar/app-vite.

  • Potential data loss due to unsafe deletion targets
  • Need to validate effective deletion targets before artifact cleanup
  • Verify build configuration to prevent data loss
  • Update to fixed version to prevent vulnerability

Technical summary

The @quasar/app-vite package recursively removes the build.distDir before producing build artifacts without checking if the path is safe, potentially leading to data loss if the configured path targets sensitive directories. 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. Defenders should prioritize validating deletion targets to prevent data loss due to this vulnerability in @quasar/app-vite.

Defensive priority

Defenders should prioritize validating the effective deletion target before every artifact cleanup to prevent data loss.

Recommended defensive actions

  • Validate the effective deletion target before every artifact cleanup
  • Always reject filesystem roots, the user home directory, and other sensitive directories
  • Verify build configuration to prevent unsafe deletion targets
  • Update to version 3.3.0 or later of @quasar/app-vite
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

Evidence from the source corpus indicates that @quasar/app-vite recursively removes build.distDir before producing build artifacts without checking the path, potentially targeting project roots, user home directories, or filesystem roots. The source item detailing the vulnerability provides further context on the issue. Official CVE Program record and NIST NVD detail page offer additional information.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-106109 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-106109

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-106109 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-106109

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.