CVE-2026-34977: Aperi'Solve Affected by Unauthenticated RCE via JPSeek Analyzer Command
Aperi'Solve is an open-source steganalysis web platform. In versions 3.1.3 through 3.2.0, when uploading a JPEG, a user can specify an optional password to accompany the JPEG. This password is then directly passed into an expect command, which is then subsequently passed into a bash -c command, without any form of sanitization or validation. An unauthenticated attacker can achieve root-level RCE inside the worker container with a single HTTP request, enabling full read/write access to all user-uploaded images, analysis results, and plaintext steganography passwords stored on disk. Because the container shares a Docker network with PostgreSQL and Redis (no authentication on either), the attacker can pivot to dump the entire database or manipulate the job queue to poison results for other users. If Docker socket mounting or host volume mounts are present, this could escalate to full host compromise. This would also include defacement of the website itself. This vulnerability is fixed in 3.2.1.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Aperi'Solveto a version that resolves this vulnerability.Fixed in 3.2.1
Event History
Frequently Asked Questions
Which releases require remediation?
Aperi'Solve versions 3.1.3 through 3.2.0 are affected. The issue is fixed in version 3.2.1.
Does exploitation require an account or user interaction?
No. An unauthenticated attacker can exploit the issue with a single HTTP request involving a JPEG upload and the optional password field.
What can an attacker access after compromising the worker container?
The attacker can obtain root-level code execution in the worker container and read or modify uploaded images, analysis results, and plaintext steganography passwords stored on disk. They can also pivot to PostgreSQL and Redis on the shared Docker network, where no authentication is present, to dump the database or manipulate queued jobs.
Under what conditions could this affect the Docker host?
Host compromise may be possible if the worker container has the Docker socket mounted or has host volume mounts. Without those conditions, the described impact includes compromise of the worker container and connected PostgreSQL and Redis services.