# CVE-2025-34195: Vasion Print (formerly PrinterLogic) Unquoted Path During Driver Installation Leads to Execution of C:\Program.exe > Attackers can achieve remote code execution and privilege escalation on Windows endpoints by exploiting unquoted paths during driver installation. - **Severity:** High 8.6 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 19 Sep 2025 - **Updated:** 15 May 2026 - **Also known as:** GHSA-5g4v-r3ch-wg6m ## What is CVE-2025-34195? CVE-2025-34195 is a high-severity vulnerability in Vasion Print Application, published on 19 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description Vasion Print (formerly PrinterLogic) Virtual Appliance Host versions prior to 1.0.735 and Application prior to 20.0.1330 (Windows client deployments) contain a remote code execution vulnerability during driver installation caused by unquoted program paths. The PrinterInstallerClient driver-installation component launches programs using an unquoted path under "C:\Program Files (x86)\Printer Properties Pro\Printer Installer". Because the path is unquoted, the operating system may execute a program located at a short-path location such as C:\Program.exe before the intended binaries in the quoted path. If an attacker can place or cause a program to exist at that location, it will be executed with the privileges of the installer process (which may be elevated), enabling arbitrary code execution and potential privilege escalation. This weakness can be used to achieve remote code execution and full compromise of affected Windows endpoints. This vulnerability has been identified by the vendor as: V-2022-006 — Driver Upload Security. Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type) ## Which versions are affected by CVE-2025-34195? It affects 2 products. Products: Vasion Virtual Appliance Application, Vasion Virtual Appliance Host. ## How do I fix CVE-2025-34195? No fix has been published for CVE-2025-34195 yet. Limit exposure of the affected software until one is available. ## Is CVE-2025-34195 being exploited? There is no known exploitation of CVE-2025-34195 in the wild and no public exploit code. ## Other vulnerabilities in Vasion Print Application - [CVE-2025-34217](https://insights.sbomify.com/CVE-2025-34217/): Vasion Print (formerly PrinterLogic) Undocumented Hardcoded SSH Key (critical 10.0) - [CVE-2025-34216](https://insights.sbomify.com/CVE-2025-34216/): Vasion Print (formerly PrinterLogic) RCE and Password Leaks via API (critical 10.0) - [CVE-2025-34218](https://insights.sbomify.com/CVE-2025-34218/): Vasion Print (formerly PrinterLogic) Exposed Internal Docker Instance (critical 10.0) - [CVE-2025-34221](https://insights.sbomify.com/CVE-2025-34221/): Vasion Print (formerly PrinterLogic) (critical 10.0) - [CVE-2025-34222](https://insights.sbomify.com/CVE-2025-34222/): Vasion Print (formerly PrinterLogic) Unauthenticated Admin APIs Used to Modify SSL Certificates (critical 10.0) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-34195 and fix it if it is affected. What it is: CVE-2025-34195 is a high-severity vulnerability in Vasion Print Application, published on 19 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-34195 in the wild and no public exploit code. Affected product: Vasion Print Application. 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-2025-34195/ (Markdown: https://insights.sbomify.com/CVE-2025-34195/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-34195 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-34195 - OSV: https://osv.dev/vulnerability/CVE-2025-34195 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-34195/ Summaries are generated and may contain mistakes; the official description above is the record.