Skip to main content
Menu
CVEs

CVE

MyMangaDB information disclosure in unauthenticated export endpoint

Affects MyMangaDB builds before 2.7.2 whose server is reachable over the network. Fixed in 2.7.2.

CVE-2026-77295Published Updated Summary written by a model

8.7HighCNA
Exploited
No known exploitation
Fix
Fixed in 2.7.2
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 2.7.2.

Summary

MyMangaDB, a self-hosted manga collection manager, has an export endpoint that requires no login, so anyone on the network can download the whole application database and cover-image library. The exposed database includes user password hashes, which an attacker can then try to crack offline. The problem affects versions before 2.7.2.

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/database/export handler in backend/app/api/v1/endpoints/database.py returns a ZIP containing the live SQLite database and the cover-image library. The database includes the users table and hashed_password values, allowing a remote attacker to obtain all application data and conduct offline password attacks without a session or token. This issue is fixed in version 2.7.2.

cve.now Index

26Pcve.now Index 26 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.7/10CVSS 8.7
  • 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
  • Would score about 31 if advisories confirm default setups are exposed

What to do

  • 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-77295 (MyMangaDB: Unauthenticated database export endpoint discloses the entire user table, including password hashes, and all cover images), 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-77295 (entry last updated 2026-11-18):
Affected:
- FabianRolfMatthiasNoll MyMangaDB: fixed in 2.7.2
Fixed versions: 2.7.2.
Vendor patches: 2ad34ea (source: https://github.com/FabianRolfMatthiasNoll/MyMangaDB/security/advisories/GHSA-66wj-vwff-vp3p). Check each asset for these patch ids, not only its version.
Conditions (all must be true for the bug to be hit):
- The /database/export endpoint is reachable over the network by the attacker (source: https://github.com/FabianRolfMatthiasNoll/MyMangaDB/security/advisories/GHSA-66wj-vwff-vp3p)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-77295 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-77295 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-66wj-vwff-vp3p
- 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-77295
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-77295"}.

Timeline

  1. CVE published
  2. First seen 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-66wj-vwff-vp3p
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-77295
RecordNVD · CVE-2026-77295
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-77295

Is CVE-2026-77295 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?

The database export endpoint can be downloaded without logging in. The exported SQLite file includes every user account with its password hash, plus all stored cover images and library content.Source: github.com

Which versions are affected by CVE-2026-77295?

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

Am I affected, and how do I check?

Versions before 2.7.2 are affected, in setups where the /database/export endpoint can be reached over the network. To check a version, look at the MyMangaDB release or package version in your installation, and check whether the server is reachable by others.Source: github.com

How do I fix CVE-2026-77295?

Upgrade to MyMangaDB 2.7.2, which adds an authentication check to the export route. The fix is tracked as patch 2ad34ea.Source: github.com

More CVEs