CVE-2025-34201: Vasion Print Virtual Appliance Host · Improper Isolation or Compartmentalization
Affects Vasion Print Virtual Appliance HostSource CVE Database V5
Not known to be exploited · CVSS 8.5 High.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Vasion Print Virtual Appliance Host | Affected
| Fixed in– |
AI-suggested
European organizations should implement the following specific mitigations: 1) Enforce strict network segmentation and firewall rules between Docker containers to prevent unauthorized lateral movement; 2) Utilize container security best practices such as running containers with the least privilege and enabling user namespaces to isolate container processes; 3) Monitor internal container network traffic for anomalous access patterns indicating lateral movement attempts; 4) Deploy runtime security tools that can detect and block suspicious container behavior; 5) Regularly audit container configurations and overlay network settings to ensure no unintended exposure of internal services; 6) Consider deploying micro-segmentation solutions to enforce granular network policies within the container environment; 7) Engage with Vasion for updates or patches and apply them promptly once available; 8) Limit the exposure of sensitive internal services (e.g., Redis, MySQL) by restricting access to only necessary containers or services; 9) Implement strong logging and alerting on container and network activity to enable rapid incident response; 10) Conduct penetration testing focused on container isolation to identify potential weaknesses before attackers do.
Description
Vasion Print (formerly PrinterLogic) Virtual Appliance Host and Application (VA and SaaS deployments) run many Docker containers on shared internal networks without firewalling or segmentation between instances. A compromise of any single container allows direct access to internal services (HTTP, Redis, MySQL, etc.) on the overlay network. From a compromised container, an attacker can reach and exploit other services, enabling lateral movement, data theft, and system-wide compromise.
References
- pierrekim.github.io/blog/2025-04-08-vasion-printerlogic-83-vulnerabilities.html (opens in a new tab)
- help.printerlogic.com/saas/Print/Security/Security-Bulletins.htm (opens in a new tab)
- help.printerlogic.com/va/Print/Security/Security-Bulletins.htm (opens in a new tab)
- vulncheck.com/advisories/vasion-print-printerlogic-lack-of-network-segmentation-between-docker-instances (opens in a new tab)