dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-3961

MEDIUM · 6.3 CVSS v3.1 Published 2026-03-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
A vulnerability was determined in zyddnys manga-image-translator up to beta-0.3. The affected element is the function to_pil_image of the file manga-image-translator-main/server/request_extraction.py of the component Translate Endpoints. This manipulation causes server-side request forgery. It is possible to initiate the attack remotely. The exploit has been publicly disclosed and may be utilized. The project was informed of the problem early through an issue report but has not responded yet.

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 · moderate confidence

Server-Side Request Forgery (SSRF) vulnerability in the to_pil_image function within manga-image-translator's request_extraction.py. The function processes image URLs from user input without proper validation, allowing attackers to make the server fetch arbitrary URLs including internal resources, potentially exposing internal services or cloud metadata endpoints.

MitigationImplement strict URL validation in to_pil_image to only allow approved URL schemes and destinations, block requests to localhost/private IP ranges (127.0.0.0/8, 10.0.0.0/8, 192.168.0.0/16, 172.16.0.0/12), and consider implementing an allowlist of permitted domains or using a dedicated image fetching service with isolation.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if manga-image-translator is installed
    Check for the presence of the manga-image-translator package or application in your environment. Look for the request_extraction.py file in the project directory.
    Affected if The application is present and contains the request_extraction.py file with the to_pil_image function
  2. Determine the installed version
    Check the version of manga-image-translator by running 'pip show manga-image-translator' or inspecting the version file in the project. Compare against any fixed version released after the CVE disclosure.
    Affected if The installed version is older than the patched version for CVE-2026-3961
  3. Verify if user-supplied URLs can reach to_pil_image
    Inspect the application code flow to determine whether the to_pil_image function processes URLs provided by end users. Check if there are API endpoints or input forms that accept image URLs and pass them to this function.
    Affected if User-provided URLs can be processed by to_pil_image without validation
  4. Check for URL validation in to_pil_image
    Review the to_pil_image function in request_extraction.py to see if it performs any validation on the input URL before fetching. Look for checks that restrict URL schemes, block private IP ranges, or validate against an allowlist.
    Affected if No URL validation exists, or validation only checks basic format without blocking internal/private addresses
  5. Test for SSRF exposure
    If you have a test environment, attempt to provide an internal URL (such as http://127.0.0.1:8080 or http://169.254.169.254) as an image URL input to see if the server attempts to fetch it.
    Affected if The server attempts to fetch internal or metadata URLs provided as input

You are affected if manga-image-translator is running and the to_pil_image function processes user-supplied image URLs without proper validation to block internal/private network requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict URL validation in to_pil_image to only allow approved URL schemes and destinations, block requests to localhost/private IP ranges (127.0.0.0/8, 10.0.0.0/8, 192.168.0.0/16, 172.16.0.0/12), and consider implementing an allowlist of permitted domains or using a dedicated image fetching service with isolation.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3961 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3961 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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