# CVE-2025-34218: Vasion Print (formerly PrinterLogic) Exposed Internal Docker Instance

> Unauthenticated attackers can access internal Docker containers via exposed gateway endpoints, leading to information disclosure, privilege escalation, or denial of service.

- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Sep 2025
- **Updated:** 15 May 2026
- **Also known as:** GHSA-662c-whx5-q24f

## What is CVE-2025-34218?

CVE-2025-34218 is a critical missing authorization vulnerability in Vasion Print Application, published on 29 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 prior to version 22.0.1049 and Application prior to version 20.0.2786 (VA/SaaS deployments) expose internal Docker containers through the gw Docker instance.  The gateway publishes a /meta endpoint which lists every micro‑service container together with version information. These containers are reachable directly over HTTP/HTTPS without any access‑control list (ACL), authentication or rate‑limiting. Consequently, any attacker on the LAN or the Internet can enumerate all internal services and their versions, interact with the exposed APIs of each microservice as an unauthenticated user, or issue malicious requests that may lead to information disclosure, privilege escalation within the container, or denial‑of‑service of the entire appliance. The root cause is the absence of authentication and network‑level restrictions on the API‑gateway’s proxy to internal Docker containers, effectively turning the internal service mesh into a public attack surface. This vulnerability has been identified by the vendor as: V-2024-030 — Exposed Internal Docker Instance (LAN).

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 2 products.


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

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

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

## Is CVE-2025-34218 being exploited?

There is no known exploitation of CVE-2025-34218 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-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)
- [CVE-2025-34223](https://insights.sbomify.com/CVE-2025-34223/): Vasion Print (formerly PrinterLogic) Insecure Installation Credentials (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-34218 and fix it if it is affected.

What it is: CVE-2025-34218 is a critical missing authorization vulnerability in Vasion Print Application, published on 29 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-34218 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-34218/ (Markdown: https://insights.sbomify.com/CVE-2025-34218/index.md)
```

## Sources

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

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