Bookmarks

    Nothing saved yet. Use the bookmark on any article. Bookmarks are kept on this device only: they stay private and work without an account.

    Settings

    Appearance

    Reading mode

    Font size

    Content width

    Line spacing

    Keyboard shortcuts

    /
    Search
    j k
    Next / previous story
    ← →
    Previous / next section (columns)
    b
    Bookmarks
    s
    Settings
    r
    Columns / scroll
    t
    Light / dark

    Saved in this browser only.

    Ping2Prompt
    Subscribe to the Weekly Brief Sign in
    MyMangaDB A Modern Manga Library

    MyMangaDB 2.7.2 fixes critical unauthenticated database export and import flaws

    Automated source check

    Docker

    Two MyMangaDB flaws rated up to CVSS 9.3

    NVD rates CVE-2026-77297 at CVSS 4.0 base score 9.3, CRITICAL, and its companion CVE-2026-77295 at 8.7, HIGH. Both affect the database export and import endpoints of MyMangaDB, a self-hosted manga collection manager. The exploitation status is unknown: neither NVD entry says whether the flaws are being exploited in the wild.

    MyMangaDB versions before 2.7.2 are exposed

    Every MyMangaDB version before 2.7.2 is affected by both CVE-2026-77295 and CVE-2026-77297. The vulnerable code sits in the /api/v1/database/export and /api/v1/database/import handlers, which require no login. If your instance runs a release older than 2.7.2 and its API is reachable by others, treat it as exposed.

    How an anonymous request takes over the database

    The attacker needs no session, token, privileges or user interaction, and can attack remotely.

    • Export (CVE-2026-77295): the handler returns a ZIP of the live SQLite database and cover images, including the users table with hashed passwords, which allows offline password attacks.
    • Import (CVE-2026-77297): the handler accepts a ZIP and moves its database file into place, so an attacker can supply a database with an administrative account and log in as it.
    • Disruption: invalid replacement data sent to the import handler can destroy application data or take the service down.

    Upgrade MyMangaDB to 2.7.2 now

    Upgrade to MyMangaDB 2.7.2, which fixes both CVEs. NVD points to the v2.7.2 release tag and fix commit 2ad34ea785c01d096b38a01420d56fc5a1078db4. No workaround is given for anyone who cannot upgrade right away. If you ran an older version with the API reachable, consider that password hashes may have been downloaded, and check for administrator accounts you did not create.

    What the NVD entries leave out

    Neither entry gives a disclosure or publication date, and they do not describe what else changed in 2.7.2. The advisory references are GHSA-66wj-vwff-vp3p for the export flaw and GHSA-6fjr-pvm2-6xw2 for the import flaw.

    Product Affected Fixed
    MyMangaDB (CVE-2026-77295) before 2.7.2 2.7.2
    MyMangaDB (CVE-2026-77297) before 2.7.2 2.7.2

    Sources

    Image: Estormiz, CC0 1.0, via Wikimedia Commons


    This story was produced with AI assistance from the sources listed above and fact-checked against them before publication. Read our editorial methodology and the corrections log. Spotted an error? Email [email protected].

    Continue

    Share on Bluesky · Mastodon · Email ·

    Discussion