CVE-2025-34221: Vasion Print (formerly PrinterLogic)

Published Sep 29, 2025
·
Updated

Vasion Print (formerly PrinterLogic) Virtual Appliance Host prior to version 25.2.169 and Application prior to version 25.2.1518 (VA/SaaS deployments) expose every internal Docker container to the network because firewall rules allow unrestricted traffic to the Docker bridge network. Because no authentication, ACL or client‑side identifier is required, the attacker can interact with any internal API, bypassing the product’s authentication mechanisms entirely. The result is unauthenticated remote access to internal services, allowing credential theft, configuration manipulation and potential remote code execution. This vulnerability has been identified by the vendor as: V-2025-002 — Authentication Bypass - Docker Instances.

Affected Software

4 affected components
Vasion Print Virtual Appliance Host<25.2.169
Vasion Print Application<25.2.1518
Vasion Virtual Appliance Application<25.2.1518
Vasion Virtual Appliance Host<25.2.169

Event History

Sep 29, 2025
CVE Published
via MITRE·08:43 PM
Data Sourced
via MITRE·08:43 PM
DescriptionWeakness
Data Sourced
via NVD·09:15 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-34221?

CVE-2025-34221 is considered a high-severity vulnerability due to the unrestricted network access it allows to internal Docker containers.

2

How do I fix CVE-2025-34221?

To fix CVE-2025-34221, you should upgrade to Vasion Print Virtual Appliance Host version 25.2.169 or later, and Vasion Print Application version 25.2.1518 or later.

3

What impact does CVE-2025-34221 have on my network?

CVE-2025-34221 can potentially allow unauthorized access to sensitive information hosted in internal Docker containers, compromising security.

4

Which versions of Vasion Print are affected by CVE-2025-34221?

Versions prior to 25.2.169 of Vasion Print Virtual Appliance Host and prior to 25.2.1518 of Vasion Print Application are affected by CVE-2025-34221.

5

Is there a workaround for CVE-2025-34221?

There are no specific workarounds; the best course of action is to upgrade to the recommended versions to mitigate the risk.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203