# CVE-2025-34193: Security feature bypass in Print Application > Vasion Print client binaries lack modern memory protections, allowing attackers to potentially achieve code execution and privilege escalation via crafted inputs. - **Severity:** High 7.1 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/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-p3jp-q7fm-cgrw ## What is CVE-2025-34193? CVE-2025-34193 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 25.1.102 and Application versions prior to 25.1.1413 include Windows client components (PrinterInstallerClientInterface.exe, PrinterInstallerClient.exe, PrinterInstallerClientLauncher.exe) that lack modern compile-time and runtime exploit mitigations and rely on outdated runtimes. These binaries are built as 32-bit, without Data Execution Prevention (DEP), Address Space Layout Randomization (ASLR), Control Flow Guard (CFG), or stack-protection, and they incorporate legacy technologies (Pascal/Delphi and Python 2) which are no longer commonly maintained. Several of these processes run with elevated privileges (NT AUTHORITY\SYSTEM for PrinterInstallerClient.exe and PrinterInstallerClientLauncher.exe), and the client automatically downloads and installs printer drivers. The absence of modern memory safety mitigations and the use of unmaintained runtimes substantially increase the risk that memory-corruption or other exploit primitives — for example from crafted driver content or maliciously crafted inputs — can be turned into remote or local code execution and privilege escalation to SYSTEM. This vulnerability has been confirmed to be remediated, but it is unclear as to when the patch was introduced. Weakness: CWE-755 (Improper Handling of Exceptional Conditions), CWE-1104 (Use of Unmaintained Third Party Components) ## Which versions are affected by CVE-2025-34193? It affects 2 products. Products: Vasion Virtual Appliance Application, Vasion Virtual Appliance Host. ## How do I fix CVE-2025-34193? No fix has been published for CVE-2025-34193 yet. Limit exposure of the affected software until one is available. ## Is CVE-2025-34193 being exploited? There is no known exploitation of CVE-2025-34193 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-34193 and fix it if it is affected. What it is: CVE-2025-34193 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-34193 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-34193/ (Markdown: https://insights.sbomify.com/CVE-2025-34193/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-34193 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-34193 - OSV: https://osv.dev/vulnerability/CVE-2025-34193 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-34193/ Summaries are generated and may contain mistakes; the official description above is the record.