CVE-2026-42213
Path Traversal in SolidCAM-GPPL-IDE
Publication date: 2026-05-08
Last updated on: 2026-05-08
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| solidcam | gppl_ide | From 1.0.0 (inc) to 1.0.2 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-200 | The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. |
| CWE-295 | The product does not validate, or incorrectly validates, a certificate. |
| CWE-918 | The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. |
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability exists in SolidCAM-GPPL-IDE, an unofficial extension for SolidCAM, specifically in versions from 1.0.0 to before 1.0.2. The issue is with the "filename" directive in GPPL postprocessor files, which is handled by GpplDocumentLinkHandler to create clickable links in VS Code. This handler accepted arbitrary file paths, including absolute paths, relative paths with parent-directory segments, UNC paths, and arbitrary subfolders, and used File.Exists to check if the file exists before rendering the link.
Because the handler accepted arbitrary paths, two attack surfaces emerged: one allowing information disclosure through File.Exists probing, and another allowing NTLM hash leaks via UNC path probing. This means an attacker could potentially gather information about the file system or cause the system to leak NTLM hashes by exploiting how the handler processes these paths.
This vulnerability was fixed in version 1.0.2 of SolidCAM-GPPL-IDE.
How can this vulnerability impact me? :
This vulnerability can impact you by allowing an attacker to perform information disclosure through probing the file system using the File.Exists method. This could reveal the presence or absence of files or directories on your system.
Additionally, the vulnerability allows for NTLM hash leaks via UNC path probing. This means an attacker could potentially capture NTLM authentication hashes, which could be used in further attacks such as credential replay or lateral movement within a network.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability has been patched in SolidCAM-GPPL-IDE version 1.0.2. Immediate mitigation involves updating the software to version 1.0.2 or later.