CVE-2026-106103

Quasar Framework: Path Traversal / Arbitrary File Write via crafted Icon Genie profile

export function getAssetsFiles(assets) {
  ...
  return list.map(({ tag, ...asset }) => {
    const file = {
      ...asset,
      relativeName: join(asset.folder, asset.name),
      absoluteName: join(appDir, asset.folder, asset.name)   // no containment check
    }
    ...
  })
}

• Type: CWE-22 Path Traversal / Arbitrary File Write
• Auth required: No network auth, local CLI trust; requires the developer to run icongenie against a profile they didn't fully author/audit themselves
• Consequence: Arbitrary file write/overwrite at any path the running user can write to, scoped by the number of .. segments, can lead to persistence (cron/shell rc file) or supply-chain-style code execution if the written file is later executed/sourced.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2026-106103 has a CVSS score of 7.1 (High). The vector is requires local access, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (6.1.1); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

import { resolve, sep } from 'node:path'

const absoluteName = resolve(appDir, asset.folder, asset.name)

if (absoluteName !== appDir && !absoluteName.startsWith(appDir + sep)) {
  fatal(`Profile asset escapes the project folder: "${asset.folder}/${asset.name}"`)
}

1. What is CVE-2026-106103? CVE-2026-106103 is a high-severity path traversal vulnerability in @quasar/icongenie (npm), affecting versions < 6.1.1. It is fixed in 6.1.1. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2026-106103? CVE-2026-106103 has a CVSS score of 7.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of @quasar/icongenie are affected by CVE-2026-106103? @quasar/icongenie (npm) versions < 6.1.1 is affected.
4. Is there a fix for CVE-2026-106103? Yes. CVE-2026-106103 is fixed in 6.1.1. Upgrade to this version or later.
5. Is CVE-2026-106103 exploitable, and should I be worried? Whether CVE-2026-106103 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-106103 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-106103? Upgrade @quasar/icongenie to 6.1.1 or later.