{"items":[{"id":"NVI-00012103","kind":"vulnerability","title":"Quasar Framework: App Vite build cleanup can recursively remove unsafe configured output directories","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-q9mq-245r-4g93","CVE-2026-106109"],"plain_summary":"GitHub lists this reviewed advisory for @quasar/app-vite. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-7a9094416e84e6ef99f3d90f3470cd5d"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-06T20:17:17.473Z","value":"4.1 MEDIUM (4.0)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-7a9094416e84e6ef99f3d90f3470cd5d"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-a7c40a6a56799960c51f36988e4e8990","url":"https://github.com/advisories/GHSA-q9mq-245r-4g93","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-q9mq-245r-4g93","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T00:58:46.232Z"},{"id":"sr-7a9094416e84e6ef99f3d90f3470cd5d","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-106109","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-106109","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-03T09:58:21.903Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-a7c40a6a56799960c51f36988e4e8990"],"technology":"@quasar/app-vite","known_exclusions":[],"conditions_summary":"## Summary\n\n`@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.\n\n## Details\n\nThe 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.\n\n`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.\n\n## Impact\n\nRunning a normal Quasar build with an unsafe `build.distDir` can delete data accessible to the build user before compilation begins.\n\n## Remediation\n\nValidate the effective deletion target before every artifact cleanup. Always reject filesystem roots, the user home directory and the pr","public_affected_ranges":[">= 1.0.0, <= 3.2.0"]}],"null_published_at":"2026-11-08T15:11:49.361Z","source_updated_at":"2026-10-07T16:14:36.000Z","source_disclosed_at":"2026-10-07T16:14:35.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-11-01T00:58:46.232Z"},{"id":"NVI-00012103","kind":"vulnerability","title":"Quasar Framework: App Vite build cleanup can recursively remove unsafe configured output directories","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-q9mq-245r-4g93","CVE-2026-106109"],"plain_summary":"GitHub lists this reviewed advisory for @quasar/app-vite. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-a7c40a6a56799960c51f36988e4e8990"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-a7c40a6a56799960c51f36988e4e8990","url":"https://github.com/advisories/GHSA-q9mq-245r-4g93","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-q9mq-245r-4g93","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T00:58:46.232Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-a7c40a6a56799960c51f36988e4e8990"],"technology":"@quasar/app-vite","known_exclusions":[],"conditions_summary":"## Summary\n\n`@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.\n\n## Details\n\nThe 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.\n\n`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.\n\n## Impact\n\nRunning a normal Quasar build with an unsafe `build.distDir` can delete data accessible to the build user before compilation begins.\n\n## Remediation\n\nValidate the effective deletion target before every artifact cleanup. Always reject filesystem roots, the user home directory and the pr","public_affected_ranges":[">= 1.0.0, <= 3.2.0"]}],"null_published_at":"2026-11-01T01:03:56.631Z","source_updated_at":"2026-10-07T16:14:36.000Z","source_disclosed_at":"2026-10-07T16:14:35.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-01T00:58:46.232Z"}],"next_cursor":null,"snapshot_revision":"42594"}