# CVE-2025-34194: Vasion Print (formerly PrinterLogic) Local Privilege Escalation via Insecure Temporary File Handling

> Local attackers can escalate privileges to SYSTEM by exploiting insecure temporary file handling in Vasion Print components via symbolic link attacks.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Sep 2025
- **Updated:** 25 May 2026
- **Also known as:** GHSA-8vvg-j3g5-33rh

## What is CVE-2025-34194?

CVE-2025-34194 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 (Windows client deployments) contain an insecure temporary-file handling vulnerability in the PrinterInstallerClient components. The software creates files as NT AUTHORITY\SYSTEM inside a directory under the control of the local user (C:\Users\%USER%\AppData\Local\Temp\). An attacker who can place symbolic links or otherwise influence filenames in that directory can cause the service to follow the link and write to arbitrary filesystem locations as SYSTEM. This allows a local, unprivileged user to overwrite or create files as SYSTEM, leading to local privilege escalation and the ability to modify configuration files, replace or inject binaries, or otherwise compromise confidentiality, integrity, and availability of the system. This vulnerability has been confirmed to be remediated, but it is unclear as to when the patch was introduced.

Weakness: CWE-59 (Improper Link Resolution Before File Access), CWE-377 (DEPRECATED: Insecure Temporary File)

## Which versions are affected by CVE-2025-34194?

It affects 2 products.


Products: Vasion Virtual Appliance Application, Vasion Virtual Appliance Host.

## How do I fix CVE-2025-34194?

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

## Is CVE-2025-34194 being exploited?

There is no known exploitation of CVE-2025-34194 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-34194 and fix it if it is affected.

What it is: CVE-2025-34194 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-34194 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-34194/ (Markdown: https://insights.sbomify.com/CVE-2025-34194/index.md)
```

## Sources

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

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