# CVE-2026-106103: Quasar Framework: Path Traversal / Arbitrary File Write via crafted Icon Genie profile

> A path traversal vulnerability in Quasar Icon Genie allows attackers to write arbitrary files via crafted profiles, potentially leading to code execution.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 6 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-wmpw-j6qv-mw88

## What is CVE-2026-106103?

CVE-2026-106103 is a high-severity path traversal vulnerability in @quasar icongenie, published on 6 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Quasar Framework is a framework for building high-performance Vue.js user interfaces. Prior to @quasar/icongenie 6.1.1, the icongenie generate --profile command accepted folder and name values from a user-supplied profile without constraining the resolved destination to the Quasar project directory. icongenie/lib/utils/get-assets-files.js joined those values with appDir, while icongenie/lib/utils/validate-profile-object.js required only non-empty strings, allowing parent-directory traversal. A developer who runs a crafted profile can cause generated image content to be written or overwritten at any path writable by that user, potentially modifying shell startup files, build scripts, or other executable configuration. This issue is fixed in version 6.1.1.

Weakness: CWE-73 (External Control of File Name or Path), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-106103?

2 open source packages ship an affected version, including @quasar/icongenie.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@quasar/icongenie` | npm | All versions | 6.1.1 |
| `@quasar/icongenie` | npm | All versions | 6.1.1 |

## How do I fix CVE-2026-106103?

Upgrade @quasar/icongenie to 6.1.1 or later.

## Is CVE-2026-106103 being exploited?

There is no known exploitation of CVE-2026-106103 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-106103 and fix it if it is affected.

What it is: CVE-2026-106103 is a high-severity path traversal vulnerability in @quasar icongenie, published on 6 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-106103 in the wild and no public exploit code.

Affected packages and fixed versions:
- @quasar/icongenie (npm): affected all versions; fixed in 6.1.1
- @quasar/icongenie (npm): affected all versions; fixed in 6.1.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-106103/ (Markdown: https://insights.sbomify.com/CVE-2026-106103/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-106103
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-106103
- OSV: https://osv.dev/vulnerability/CVE-2026-106103

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-106103/
Summaries are generated and may contain mistakes; the official description above is the record.