critical CVSS 9.8

CVE-2025-34215·Docker vulnerability

Vasion Print (formerly PrinterLogic) Virtual Appliance Host prior to version 22.0.1026 and Application prior to version 20.0.2702 (only VA deployments) expose an unauthenticated firmware-upload flow: a public page returns a signed token usable at va-api/v1/update, and every Docker image contains the appliance’s private GPG key and hard-coded passphrase. An attacker who extracts the key and obtains a token can decrypt, modify, re-sign, upload, and trigger malicious firmware, gaining remote code execution. This vulnerability has been identified by the vendor as: V-2024-020 — Remote Code Execution.

Severity
critical
Software
Docker
Fixed in
22.0.1026
Published
2025-09-29

Affected versions

Until: 22.0.1026

Fixed in: 22.0.1026

How to fix this CVE

Update Docker to version 22.0.1026 or later to patch the unauthenticated firmware upload vulnerability in Vasion Print Virtual Appliance deployments. This critical flaw allows attackers to extract embedded cryptographic keys from Docker images and upload malicious firmware without authentication, leading to remote code execution. Organizations running affected versions should prioritize this update immediately.

sudo dnf update docker-ce

Defensia detects this vulnerability

What an exploitation attempt looks like

Sample log line indicative of exploitation attempts:

POST /va-api/v1/update with firmware binary payload and Authorization header containing valid signed token; responses indicating successful firmware decryption and installation; subsequent container restart or process execution from /var/lib/docker or /opt/vasion directories

WAF mitigation (if patching is not yet possible)

Add this rule to your WAF to block exploitation attempts while you schedule the patch. 

Block unauthenticated POST requests to /va-api/v1/update and related firmware endpoints; require multi-factor authentication and IP whitelisting for any firmware update flows; implement request signing verification and rate limiting on token generation endpoints; reject firmware uploads unless digitally signed with current vendor certificates

How to check if you are affected

  1. Run 'docker --version' to check your installed Docker version and compare against 22.0.1026
  2. If running Vasion Print Virtual Appliance, inspect the container image for embedded private GPG keys using 'docker image inspect <image-id> | grep -i gpg' or by mounting and examining /etc/pki/ or similar key storage directories
  3. Search application logs and Docker daemon logs for POST requests to endpoints matching '/va-api/v1/update' or firmware-related upload endpoints using 'grep -r 'va-api/v1/update' /var/log/'
  4. Verify the patched version by running 'docker --version' again and confirming it returns 22.0.1026 or higher

FAQ

What is CVE-2025-34215?

CVE-2025-34215 is a critical remote code execution vulnerability in Vasion Print (formerly PrinterLogic) Virtual Appliance that exposes an unauthenticated firmware upload endpoint. Attackers can extract the appliance's private GPG key from Docker images and use a publicly obtainable signed token to upload, decrypt, and execute malicious firmware.

Is CVE-2025-34215 being actively exploited?

According to CISA KEV data, CVE-2025-34215 is not currently listed as actively exploited in the wild. However, no public exploit availability does not reduce the criticality of this vulnerability, which carries a CVSS score of 9.8.

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

The vulnerability affects Vasion Print Virtual Appliance Host versions prior to 22.0.1026 and Application versions prior to 20.0.2702 (VA deployments only). All Docker images shipped with affected versions contain the hardcoded private cryptographic material.

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

Run 'docker --version' and verify the version number is 22.0.1026 or later. For Vasion Print deployments, additionally check for the presence of unauthenticated access to firmware update endpoints and inspect image layers for embedded GPG keys using 'docker image inspect <image-id>'.

Does Defensia detect CVE-2025-34215?

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

Related Docker CVEs

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-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-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-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.

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

Get started free