Skip to main content
Menu
CVEs

CVE

MyMangaDB arbitrary file write via path traversal in cover uploads

MyMangaDB 2.7.1 and earlier are affected when the image and database paths sit as siblings under the same base directory, as in the default layout. Fixed in 2.7.2.

CVE-2026-77296EUVD-2026-129191Published Updated Summary written by a model

9.3CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 2.7.2
Who is exposed
Default setups

Do first: Check every install: default setups are affected.

Summary

MyMangaDB, a self-hosted manga collection manager, has a path traversal flaw in its cover-image upload handler that lets unauthenticated remote attackers write arbitrary files. By overwriting the live database, an attacker could plant an administrative user and take full control of the application, with loss of availability as well.

Original description

MyMangaDB is a self-hosted manga collection manager with automatic metadata, MyAnimeList import, Docker support, and collection statistics. Prior to 2.7.2, the unauthenticated /api/v1/images/manga/save handler in backend/app/api/v1/endpoints/image.py accepts a client-controlled filename and joins it to IMAGE_SAVE_PATH without confining the result. Traversal sequences can escape the image directory and overwrite process-writable files, including DATABASE_PATH for the live SQLite database, while the client-supplied image content type does not validate the uploaded bytes. An attacker can replace the database to plant an administrative user and can overwrite other writable files, causing full application compromise and availability loss. This issue is fixed in version 2.7.2.

Who should check

Teams running MyMangaDB 2.7.1 or earlier, self-hosted with Docker or non-Docker installs, reachable over the network

“Affected versions <= 2.7.1”

github.com

cve.now Index

31Pcve.now Index 31 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure22/25Default setups, reachable over the network without a login
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.3/10CVSS 9.3
  • No patch0/5No signal

What would change the score

  • Would score about 71 if added to CISA KEV
  • Would score about 66 if CISA's SSVC rates exploitation active

What to do

  • Check every install: default setups are affected.

  • Upgrade to a fixed version: 2.7.2.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-77296 (MyMangaDB: Unauthenticated path traversal in cover-image upload allows arbitrary file write, escalating to the same database-overwrite…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-77296 (entry last updated 2026-11-18):
Affected:
- FabianRolfMatthiasNoll MyMangaDB: fixed in 2.7.2
Fixed versions: 2.7.2.
Conditions (all must be true for the bug to be hit):
- MyMangaDB version 2.7.1 and earlier (source: https://github.com/FabianRolfMatthiasNoll/MyMangaDB/security/advisories/GHSA-66h5-6vhv-5w76)
- Image and database paths sit as siblings under the same base directory, as in the default layout (source: https://github.com/FabianRolfMatthiasNoll/MyMangaDB/security/advisories/GHSA-66h5-6vhv-5w76)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-77296 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-77296 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/FabianRolfMatthiasNoll/MyMangaDB/security/advisories/GHSA-66h5-6vhv-5w76
- https://github.com/FabianRolfMatthiasNoll/MyMangaDB/commit/2ad34ea785c01d096b38a01420d56fc5a1078db4
- https://github.com/FabianRolfMatthiasNoll/MyMangaDB/releases/tag/v2.7.2
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-77296
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-77296"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now

Affected versions

  • FabianRolfMatthiasNoll MyMangaDB

    fixed in 2.7.2

Evidence 5

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · FabianRolfMatthiasNoll/MyMangaDB · Advisory GHSA-66h5-6vhv-5w76
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-77296
RecordNVD · CVE-2026-77296
Other links 2
RepositoryGitHub · FabianRolfMatthiasNoll/MyMangaDB · Commit 2ad34ea7
RepositoryGitHub · FabianRolfMatthiasNoll/MyMangaDB · Release v2.7.2

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-77296

Is CVE-2026-77296 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

An unauthenticated request can write arbitrary files to the server's filesystem through the cover-image upload path traversal. Because the database sits beside the image directory, this can reach and overwrite the live database, letting an attacker plant an admin user and log in.Source: github.com

Which versions are affected by CVE-2026-77296?

MyMangaDB: before 2.7.2.Source: cve.now feed data

Am I affected, and how do I check?

Versions 2.7.1 and earlier are affected, and only in a setup where the image and database paths are siblings under the same base directory, as in the default layout. To check, look at the MyMangaDB version and at the IMAGE_SAVE_PATH and DATABASE_PATH settings to see whether they share a base directory.Source: github.com

How do I fix CVE-2026-77296?

Upgrade to MyMangaDB 2.7.2, the fixed version.Source: github.com

More CVEs