high CVSS 7.5 EPSS 0.38%

CVE-2025-34234·Docker vulnerability

Vasion Print (formerly PrinterLogic) Virtual Appliance Host prior to version 25.1.102 and Application prior to version 25.1.1413 (VA/SaaS deployments) contain two hardcoded private keys that are shipped in the application containers (printerlogic/pi, printerlogic/printer-admin-api, and printercloud/pi). The keys are stored in clear text under /var/www/app/config/ as keyfile.ppk.dev and keyfile.saasid.ppk.dev. The application uses these keys as the symmetric secret for AES‑256‑CBC encryption/decryption of the “SaaS Id” (external identifier) through the getEncryptedExternalId() / getDecryptedExternalId() methods. Because the secret is embedded in the deployed image, any attacker who can obtain a copy of the Docker image, read the configuration files, or otherwise enumerate the filesystem can recover the encryption key. This vulnerability has been confirmed to be remediated, but it is unclear as to when the patch was introduced.

Severity
high
Software
Docker
Fixed in
25.1.102
Published

How likely is exploitation

FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.38% — higher than 30% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.

Read the two together. CVE-2025-34234 scores 7.5 on CVSS, so a successful attack would be serious — but at 0.38%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.

Affected versions

Until: 25.1.102

Fixed in: 25.1.102

How to fix this CVE

Upgrade Docker to version 25.1.102 or later to eliminate hardcoded encryption keys embedded in container images. This vulnerability affects Vasion Print (formerly PrinterLogic) deployments where symmetric encryption secrets are stored in plain text within Docker images, allowing attackers with filesystem access to recover sensitive keys. Immediately patch all affected Docker instances and regenerate any encryption keys that may have been compromised.

sudo dnf update docker-ce

Defensia detects this vulnerability

How to check if you are affected

  1. Step 1: Check your installed Docker version with `docker --version` and compare against the vulnerable range (prior to 25.1.102)
  2. Step 2: For Vasion Print/PrinterLogic deployments, inspect running container images using `docker inspect <container_id>` and verify the image tag is not from affected versions
  3. Step 3: Scan for exposed encryption keys by checking mounted volumes: `docker exec <container_id> ls -la /var/www/app/config/ | grep -E 'keyfile\.(ppk\.dev|saasid\.ppk\.dev)'`
  4. Step 4: After updating, confirm the patched version with `docker --version` and verify container images have been rebuilt and redeployed from updated base images

Indicators of compromise

  • /var/www/app/config/keyfile.ppk.dev
  • /var/www/app/config/keyfile.saasid.ppk.dev
  • printerlogic/pi container image
  • printerlogic/printer-admin-api container image
  • printercloud/pi container image

FAQ

What is CVE-2025-34234?

CVE-2025-34234 is a critical vulnerability in Vasion Print/PrinterLogic Docker images where symmetric encryption keys used for AES-256-CBC encryption are hardcoded in plain text files within the container filesystem. This allows any attacker with access to the Docker image or container filesystem to extract the encryption keys and decrypt sensitive SaaS identifiers.

Is CVE-2025-34234 being actively exploited?

No, CVE-2025-34234 is not listed in CISA's Known Exploited Vulnerabilities (KEV) catalog and no public exploits are currently available. However, the hardcoded key design makes exploitation trivial for threat actors with container access.

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

The vulnerability affects Vasion Print Virtual Appliance Host versions prior to 25.1.102 and Application versions prior to 25.1.1413 (VA/SaaS deployments). The affected container images are printerlogic/pi, printerlogic/printer-admin-api, and printercloud/pi.

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

Run `docker images | grep -E 'printerlogic|printercloud'` to identify affected images, then inspect the container filesystem with `docker run --rm <image_name> cat /var/www/app/config/keyfile.ppk.dev` to verify if hardcoded keys are present.

Does Defensia detect CVE-2025-34234?

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

Related Docker CVEs

CVE-2026-42298CVSS 10Postiz is an AI social media scheduling tool. Prior to commit da44801, a "Pwn Request" vulnerability in the Build and Publish PR Docker Image workflow (.github/workflows/pr-docker-build.yml) allows any unauthenticated user to execute arbitrary code during the Docker build process and exfiltrate a highly privileged GITHUB_TOKEN (write-all permissions). This can be achieved simply by opening a Pull Request from a fork with a maliciously modified Dockerfile.dev. This issue has been patched via commit da44801.
CVE-2026-57572CVSS 10Crawl4AI is an open-source LLM-friendly web crawler and scraper. Prior to 0.9.0, the Docker API server accepted request-supplied browser_config.extra_args, which flowed into Chromium's launch arguments. An attacker could inject Chromium switches that replace a child-process launch command together with --no-zygote, causing Chromium to fork or exec an attacker-controlled command as the container's runtime user. The Docker API is unauthenticated by default, so a single request yields arbitrary command execution. This issue is fixed in version 0.9.0.
CVE-2026-44182CVSS 10Jupyter Enterprise Gateway launches remote Jupyter Notebook kernels across distributed clusters like Apache Spark, Kubernetes, and Docker Swarm. In versions prior to 3.3.0, the server interpolates untrusted environment variables (e.g., KERNEL_XXX) into Kubernetes manifests without YAML-aware escaping, enabling YAML injection attacks. Attackers can inject new fields, overwrite critical fields (e.g., duplicate securityContext keys, where the last one prevails), and inject document boundaries (--- for new documents, ... for end-of-document) to generate multiple resources, potentially creating arbitrary types, such as privileged pods. The Jinja2 template for the Kubernetes manifest contains several kernel_xxx variables, such as kernel_working_dir that are used when rendering the manifest and are all vectors for YAML injection. This issue has been fixed in version 3.3.0.
CVE-2026-44181CVSS 10Jupyter Enterprise Gateway launches remote Jupyter Notebook kernels across distributed clusters like Apache Spark, Kubernetes, and Docker Swarm. In versions 2.0.0rc2 and above, prior to 3.3.0, the environment variables (KERNEL_XXX) used during the rendering of the Kubernetes manifest are vulnerable to Server Side Template Injection (SSTI). By including Jinja2 template expressions it is possible to execution Python code and OS Commands in the Enterprise Gateway service. The code can use or steal the Kubernetes service account token, which can steal Kubernetes secrets and be used to fully compromise the Kubernetes cluster by scheduling a privileged pod or a pod with a hostPath volume mount. This issue has been fixed in version 3.3.0.
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.

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-34234. Free for 1 server.

Get started free