# CVE-2026-10094: Path traversal in SOLIDWORKS Visualize

> An attacker can write arbitrary files on the server via a path traversal vulnerability in SOLIDWORKS Visualize.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jun 2026
- **Updated:** 17 Jun 2026
- **Also known as:** GHSA-x4wr-mm5h-p7mm

## What is CVE-2026-10094?

CVE-2026-10094 is a critical path traversal vulnerability in Dassault Systèmes SOLIDWORKS Visualize, published on 17 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Path Traversal vulnerability affecting SOLIDWORKS Visualize from SOLIDWORKS Desktop Release 2024 through SOLIDWORKS Desktop Release 2026 could allow an attacker to write arbitrary files on the server.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

No fix has been published for CVE-2026-10094 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-10094 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-10094 is a critical path traversal vulnerability in Dassault Systèmes SOLIDWORKS Visualize, published on 17 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-10094 in the wild and no public exploit code.

Affected product: Dassault Systèmes SOLIDWORKS Visualize. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-10094/ (Markdown: https://insights.sbomify.com/CVE-2026-10094/index.md)
```

## Sources

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

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