Quick answers
- Is CVE-2026-44776 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44776 being exploited in the wild.
- How severe is CVE-2026-44776?
- Informational severity, with a CVSS score of 5.9, published 26 May 2026.
- Which products and versions are affected?
- Kareadita Kavita < 0.9.0.
- Is there a fix for CVE-2026-44776?
- A patch was published on 2026-05-26: Fixed in version 0.9.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-44776 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-44776?
- Check whether you run Kareadita Kavita at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an Insecure Direct Object Reference (IDOR) (CWE-639) within the `DownloadController` and `ChapterController`. While these controllers enforce a general 'Download' role policy, they fail to verify if the authenticated user has been granted access to the specific library containing the requested `chapterId`, `volumeId`, or `seriesId`. Because Kavita uses sequential integer IDs for these entities, an authenticated attacker can enumerate IDs to download full file contents, query file sizes, and leak chapter metadata via endpoints such as `/api/Download/volume` and `/api/Chapter`. The fix, introduced in version 0.9.0, implements library-scoped filtering using existing `HasAccessToLibrary` and `HasAccessToSeries` helpers.
Affected products
- Kareadita Kavita < 0.9.0
Timeline
- 2026-05-05: advisory: GitHub Security Lab advisory published
- 2026-05-26: disclosed: CVE published to NVD
- 2026-05-26: patched: Fixed in version 0.9.0