CVE-2026-10094
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA path traversal vulnerability in SOLIDWORKS Visualize (versions 2024 through 2026) allows attackers to write arbitrary files to the server by manipulating file paths using '../' sequences to escape intended directories. This enables remote code execution or system compromise via unauthorized file creation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify SOLIDWORKS Visualize installationCheck for SOLIDWORKS Visualize in installed programs (Windows: Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | DisplayName' in PowerShell)Affected if SOLIDWORKS Visualize is present on the system
-
Determine installed versionOpen SOLIDWORKS Visualize, go to Help > About, or check the installation directory for version info (typically in C:\Program Files\SOLIDWORKS Visualize\)Affected if Version is 2024, 2025, or 2026 (any patch version within these years)
-
Identify exposed file export interfacesCheck for any integrations, API endpoints, or batch processing tools that allow external file inputs to be saved through Visualize (look for scripts, plugins, or web services using Visualize SDK)Affected if Any feature allows external users or processes to specify output file paths
-
Inspect file operation logs for traversal patternsReview Visualize logs (typically in AppData\Roaming\SOLIDWORKS\Visualize\Logs\) and any associated server logs for sequences like '..\' or '../' in file path parametersAffected if Log entries contain '../' or '..\' sequences in file path fields
-
Audit file write permissionsCheck the directories where Visualize has write access, particularly any directories exposed to external inputs or network sharesAffected if Visualize can write to directories outside its intended output folder
If SOLIDWORKS Visualize versions 2024-2026 is installed AND exposed file save/export features accept external path input, the environment is likely vulnerable to path traversal attacks.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor patches when available; implement strict input validation and whitelist-based file path controls to prevent directory traversal sequences in all file operations.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10094 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-10094 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data