CVE-2026-10042
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedmanga-image-translator contains a remote code execution vulnerability in the shared API server mode due to unsafe deserialization of untrusted pickle data in the share.py module, where the /execute/{method_name} and /simple_execute/{method_name} endpoints deserialize attacker-controlled HTTP request bodies using pickle.loads(). A remote attacker can supply a crafted pickle payload to these endpoints to execute arbitrary code in the server process, resulting in full container compromise when running in the default Docker deployment as root.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe application deserializes HTTP request bodies using pickle.loads() on the /execute/{method_name} and /simple_execute/{method_name} endpoints in share.py without validating the input. An attacker can send a malicious pickle payload that, when deserialized, executes arbitrary code on the server, leading to full container compromise when running as root.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the manga-image-translator installationFind the share.py file in the application directory, typically in the project root or src folder. If running in Docker, identify the container image name and inspect its filesystem.Affected if The share.py file exists in the application deployment
-
Verify the vulnerable pickle code existsSearch inside share.py for pickle.loads() calls, specifically targeting the /execute/ and /simple_execute/ endpoint handlers that directly deserialize HTTP request bodies.Affected if The code contains unpickled HTTP request body data without validation
-
Confirm the API server is exposedCheck if the share.py API server is running and accessible on a network port. Look for the Flask/FastAPI app initialization that mounts the /execute/{method_name} and /simple_execute/{method_name} routes.Affected if The API endpoints are listening and reachable over the network
-
Check if running in Docker as rootIf deployed via Docker, inspect the container process: run 'docker inspect <container_id> | grep User' or check if the process runs with UID 0 (root).Affected if The container is running as root user (UID 0)
-
Compare your installed versionCheck the installed version of manga-image-translator against any available version history. Use 'pip show manga-image-translator', git tag, or inspect the Docker image tag.Affected if Your version contains the vulnerable share.py with unsafe pickle deserialization
You are affected if your manga-image-translator deployment exposes the share.py API server with unpickled HTTP request bodies and runs as root in Docker.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace pickle.loads() with safe deserialization methods (JSON, msgpack) and implement input validation. If the API must remain exposed, restrict network access and run the container as a non-root user.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10042 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-10042 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data