# CVE-2025-34191: Vasion Print (formerly PrinterLogic) Arbitrary File Write as Root via Response Path Symlink Follow

> Local attackers can exploit symlink following in response file handling to write arbitrary files as root, leading to privilege escalation and system compromise.

- **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:** 15 May 2026
- **Also known as:** GHSA-73h4-4m3x-58h5

## What is CVE-2025-34191?

CVE-2025-34191 is a high-severity path traversal 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 22.0.843 and Application prior to 20.0.1923 (macOS/Linux client deployments) contain an arbitrary file write vulnerability via the response file handling. When tasks produce output the service writes response data into files under /opt/PrinterInstallerClient/tmp/responses/ reusing the requested filename. The service follows symbolic links in the responses directory and writes as the service user (typically root), allowing a local, unprivileged user to cause the service to overwrite or create arbitrary files on the filesystem as root. This can be used to modify configuration files, replace or inject binaries or drivers, and otherwise achieve local privilege escalation and full system compromise. This vulnerability has been identified by the vendor as: V-2023-019 — Arbitrary File Write as Root.

Weakness: CWE-59 (Improper Link Resolution Before File Access), CWE-276 (Incorrect Default Permissions)

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

It affects 2 products.


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

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

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

## Is CVE-2025-34191 being exploited?

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

What it is: CVE-2025-34191 is a high-severity path traversal 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-34191 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-34191/ (Markdown: https://insights.sbomify.com/CVE-2025-34191/index.md)
```

## Sources

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

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