high CVSS 8.8

CVE-2025-34202·Docker vulnerability

Vasion Print (formerly PrinterLogic) Virtual Appliance Host prior to 25.2.169 and Application prior to 25.2.1518 (VA and SaaS deployments) expose Docker internal networks in a way that allows an attacker on the same external L2 segment — or an attacker able to add routes using the appliance as a gateway — to reach container IPs directly. This grants access to internal services (HTTP APIs, Redis, MySQL, etc.) that are intended to be isolated inside the container network. Many of those services are accessible without authentication or are vulnerable to known exploitation chains. As a result, compromise of a single reachable endpoint or basic network access can enable lateral movement, remote code execution, data exfiltration, and full system compromise. This vulnerability has been identified by the vendor as: V-2025-003 — Insecure Access to Docker Instance from WAN.

Severity
high
Software
Docker
Fixed in
25.2.169
Published
2025-09-19

Affected versions

Until: 25.2.169

Fixed in: 25.2.169

How to fix this CVE

Update Vasion Print (formerly PrinterLogic) Virtual Appliance Host to version 25.2.169 or later, and the Application component to version 25.2.1518 or later for SaaS deployments. This patch restricts direct Layer 2 access to Docker internal networks, preventing unauthorized exposure of containerized services such as Redis, MySQL, and internal HTTP APIs. Verify all instances are updated before redeploying to production environments.

sudo dnf update docker-ce

Defensia detects this vulnerability

What an exploitation attempt looks like

Sample log line indicative of exploitation attempts:

POST /redis:6379 or GET /mysql:3306 or GET /internal_api from non-whitelisted external IP; alternatively, ARP requests probing for container gateway followed by direct TCP connections to ports 3306, 6379, 8080 on container CIDR blocks

How to check if you are affected

  1. Run 'docker --version' to check the installed Docker version; versions prior to the patched release are affected if part of a Vasion Print deployment
  2. Execute 'docker network ls' and 'docker network inspect <network_name>' to enumerate internal networks and verify isolation rules are properly configured
  3. Review Docker daemon logs at '/var/lib/docker/containers/*/json.log' and system logs at '/var/log/docker.log' for unusual container-to-container communication or failed authentication attempts on internal services
  4. Confirm the patched version is running by verifying the Docker daemon reports the updated version and by checking Vasion Print application logs for V-2025-003 vulnerability remediation confirmation

FAQ

What is CVE-2025-34202?

CVE-2025-34202 is a high-severity vulnerability in Vasion Print where Docker internal networks are improperly exposed to external Layer 2 segments, allowing attackers with network access to reach isolated containerized services like databases and APIs without authentication, leading to potential remote code execution and system compromise.

Is CVE-2025-34202 being actively exploited?

No, CVE-2025-34202 is not currently listed in CISA's Known Exploited Vulnerabilities catalog, and no public exploit code is available. However, the vulnerability requires only network-layer access and basic tooling, making it likely to be targeted once widely known.

What versions of Docker are affected by CVE-2025-34202?

The vulnerability affects Vasion Print Virtual Appliance Host prior to version 25.2.169 and Application versions prior to 25.2.1518. All deployments running these earlier versions are vulnerable regardless of the underlying Docker version.

How do I check if my server is vulnerable to CVE-2025-34202?

Run 'docker network inspect bridge' and check if any internal container IPs are routable from external network segments. Additionally, verify your Vasion Print version with 'docker exec <container_id> /opt/printerlogic/version' and confirm it is 25.2.169 or later for VA or 25.2.1518+ for SaaS.

Does Defensia detect CVE-2025-34202?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Docker is installed on a monitored server running Vasion Print, CVE-2025-34202 will appear in your dashboard with remediation steps and patch availability.

Related Docker CVEs

CVE-2026-40281CVSS 10Gotenberg is a Docker-powered stateless API for PDF files. In versions 8.30.1 and earlier, the metadata write endpoint validates metadata keys for control characters but leaves metadata values unsanitized. A newline character in a metadata value splits the ExifTool stdin line into two separate arguments, allowing injection of arbitrary ExifTool pseudo-tags such as -FileName, -Directory, -SymLink, and -HardLink. This is a bypass of the incomplete key-sanitization fix introduced in v8.30.1. An unauthenticated attacker can rename or move any PDF being processed to an arbitrary path in the container filesystem, overwrite arbitrary files, or create symlinks and hard links at arbitrary paths.
CVE-2026-53576CVSS 10Kestra is an open-source, event-driven orchestration platform. Prior to 1.0.45 and 1.3.21, the authentication filter for the REST API (@Filter("/api/v1/**")) treats any request whose path ends in /configs as the public instance-config endpoint and forwards it without a credential check. kestra addresses its resources by URL path segments that the caller chooses (/api/v1/{tenant}/flows/{namespace}, /api/v1/{tenant}/executions/{namespace}/{id}, /api/v1/{tenant}/namespaces/{namespace}/kv/{key}). An anonymous caller picks the literal configs as the final segment, and the request bypasses Basic-Auth entirely. Because the bypass reaches the flow-create and execution-trigger routes, an unauthenticated caller creates a flow containing a Shell or Process task and runs it. The task executes as root inside the kestra container. The official docker-compose.yml mounts /var/run/docker.sock, so root in the container reaches the host Docker daemon. This vulnerability is fixed in 1.0.45 and 1.3.21.
CVE-2026-26216CVSS 10Crawl4AI versions prior to 0.8.0 contain a remote code execution vulnerability in the Docker API deployment. The /crawl endpoint accepts a hooks parameter containing Python code that is executed using exec(). The __import__ builtin was included in the allowed builtins, allowing unauthenticated remote attackers to import arbitrary modules and execute system commands. Successful exploitation allows full server compromise, including arbitrary command execution, file read and write access, sensitive data exfiltration, and lateral movement within internal networks.
CVE-2026-44329CVSS 10free5GC is an open-source implementation of the 5G core network. Prior to 4.2.2, free5GC's SMF mounts the UPI management route group without OAuth2/bearer-token authorization middleware. A network attacker who can reach SMF on the SBI can hit UPI endpoints with no Authorization header at all, and the requests reach the SMF business handlers. In the running Docker lab this was directly demonstrated for read (GET /upi/v1/upNodesLinks), write (POST /upi/v1/upNodesLinks with attacker-controlled UP-node and link payload), and delete (DELETE /upi/v1/upNodesLinks/{nodeID}) operations. This vulnerability is fixed in 4.2.2.
CVE-2026-33587CVSS 10Lack of user input sanitisation in Open Notebook v1.8.3 allows the application user to execute Python code (and subsequently OS commands) on the docker container via Server-Side Template Injection (SSTI) for user-created transformations.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2025-34202. Free for 1 server.

Get started free