CVE-2026-34977: Aperi'Solve Affected by Unauthenticated RCE via JPSeek Analyzer Command

Published Apr 6, 2026
·
Updated

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

2 affected components
Aperi'Solve Aperi'Solve<3.2.1
Aperisolve Aperisolve<=3.2.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Aperi'Solve to a version that resolves this vulnerability.

    Fixed in 3.2.1

Event History

Apr 6, 2026
CVE Published
via MITRE·04:16 PM
Data Sourced
via MITRE·04:16 PM
DescriptionWeakness
Data Sourced
via NVD·05:17 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

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.

2

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.

3

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.

4

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.

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