Path Traversal in @quasar/icongenie (CVE-2026-106103)
Summary
Path traversal in @quasar/icongenie (CVE-2026-106103). Data can be tampered with by attackers. Exploitable via assetsSchema. Mitigation: upgrade to 6.1.1 or later.
Original description
The description as published by the source.
Vulnerability Details
File: icongenie/lib/utils/get-assets-files.js (line 35, absoluteName: join(appDir, asset.folder, asset.name))
Validation gap: icongenie/lib/utils/validate-profile-object.js (assetsSchema) — folder/name only checked with Joi.string().required().min(1), no restriction on .. sequences or absolute paths
Entry point: icongenie/lib/runner/generate.js (generate(argv)) — profile.assets = userProfile.assets, loaded verbatim from a user-supplied JSON file via --profile
Root Cause
icongenie generate --profile loads a JSON "profile" describing icon/splashscreen assets to generate, where each asset entry has a folder/name describing where the generated file should be written relative to the Quasar project directory (appDir). getAssetsFiles() builds the write target with join(appDir, asset.folder, asset.name). Node's path.join normalizes .. segments arithmetically and does not clamp the result to stay inside appDir. The only validation before this (validateProfileObject → Joi assetsSchema) checks that folder/name are non-empty strings, with no .. rejection and no containment check against appDir.
A profile setting folder: "../../../../../../tmp/pwned-by-icongenie" sails through validation unmodified, and the generator writes attacker-influenced icon/splashscreen content to that path via a direct writeFile/sharp().toFile() call.
Attack Scenario
- Attacker publishes a "ready-made I…
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-106103 has been found in @quasar/icongenie.
Attackers can target a specific entry point like assetsSchema over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.1/10.
What to do: upgrade @quasar/icongenie to 6.1.1 or later.
If unsure, ask your IT team or search "@quasar/icongenie CVE-2026-106103" on the vendor's site.
CVE-2026-106103 (@quasar/icongenie) — CWE-22 / CVSS v3 7.1
Attack vector: local / unauthenticated
Attack surface: assetsSchema / folder / name / appDir
Patched: 6.1.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in @quasar/icongenie. Attackers reach the vulnerable code path via assetsSchema without authentication.
Check the vendor advisory for the affected versions of @quasar/icongenie. Attack surface: assetsSchema / folder / name / appDir.
Severity: High (CVSS 7.1/10). Data can be tampered with by attackers.
Update to 6.1.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@quasar/icongenie' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@quasar/icongenie' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@quasar/icongenieを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @quasar/icongenie to 6.1.1ステージング環境で 6.1.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com