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

> Unauthenticated attackers can execute arbitrary commands as root via unsanitized input in the JPSeek analyzer, leading to full system compromise and data theft.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Apr 2026
- **Updated:** 22 Jun 2026
- **Also known as:** GHSA-8r22-62p7-9jrp

## What is CVE-2026-34977?

CVE-2026-34977 is a critical command injection vulnerability in Zeecka AperiSolve, published on 6 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-34977?

It affects 1 product.


Products: Aperisolve Aperisolve.

## How do I fix CVE-2026-34977?

No fix has been published for CVE-2026-34977 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-34977 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34977 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-34977 and fix it if it is affected.

What it is: CVE-2026-34977 is a critical command injection vulnerability in Zeecka AperiSolve, published on 6 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34977 exists.

Affected product: Zeecka AperiSolve. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-34977/ (Markdown: https://insights.sbomify.com/CVE-2026-34977/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-34977
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-34977
- OSV: https://osv.dev/vulnerability/CVE-2026-34977

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-34977/
Summaries are generated and may contain mistakes; the official description above is the record.