# CVE-2025-34203: Vasion Print (formerly PrinterLogic) Use of Outdated, End-Of-Life, and Vulnerable Third-Party Components

> Vasion Print appliances use outdated, vulnerable third-party components in Docker containers, increasing attack surface and enabling potential exploitation chains.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Sep 2025
- **Updated:** 15 May 2026
- **Also known as:** GHSA-m44j-8pgf-x54w

## What is CVE-2025-34203?

CVE-2025-34203 is a critical vulnerability in Vasion Print Application, published on 19 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vasion Print (formerly PrinterLogic) Virtual Appliance Host versions prior to 22.0.1002 and Application versions prior to 20.0.2614 (VA and SaaS deployments) contain multiple Docker containers that include outdated, end-of-life, unsupported, or otherwise vulnerable third-party components (examples: Nginx 1.17.x, OpenSSL 1.1.1d, various EOL Alpine/Debian/Ubuntu base images, and EOL Laravel/PHP libraries). These components are present across many container images and increase the product's attack surface, enabling exploitation chains when leveraged by an attacker. Multiple distinct EOL versions and unpatched libraries across containers; Nginx binaries date from 2019 in several images and Laravel versions observed include EOL releases (for example Laravel 5.5.x, 5.7.x, 5.8.x). This vulnerability has been identified by the vendor as: V-2024-014 — Outdated Dependencies.

Weakness: CWE-1395 (Dependency on Vulnerable Third-Party Component)

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

It affects 2 products.


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

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

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

## Is CVE-2025-34203 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-34203 exists.

## 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-34203 and fix it if it is affected.

What it is: CVE-2025-34203 is a critical vulnerability in Vasion Print Application, published on 19 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-34203 exists.

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

## Sources

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

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