dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2026-44775

MEDIUM · 6.9 CVSS v4.0 Published 2026-05-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Kavita is a cross platform reading server. Prior to 0.9.0, the ReaderController.GetImage endpoint is decorated with [AllowAnonymous], allowing completely unauthenticated access to page images from any chapter in any library. While the endpoint accepts an apiKey parameter, it is never validated. Since entity IDs are sequential integers, an unauthenticated attacker can trivially enumerate all content on the server. This vulnerability is fixed in 0.9.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The ReaderController.GetImage endpoint in Kavita versions prior to 0.9.0 is decorated with [AllowAnonymous], permitting unauthenticated access to all page images across any library. Although the endpoint accepts an apiKey parameter, this parameter is never validated, and because entity IDs are sequential integers, attackers can trivially enumerate and access all content on the server without any credentials.

MitigationUpgrade Kavita to version 0.9.0 or later, which removes the [AllowAnonymous] attribute and properly implements authentication validation on the GetImage endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Kavita installation and version
    Locate the Kavita installation directory or check the running service. Common paths include /opt/kavita, /var/lib/kavita, or the service's version endpoint if available. Compare the installed version to the affected range: versions prior to 0.9.0 are vulnerable.
    Affected if The installed Kavita version is earlier than 0.9.0
  2. Locate the Kavita configuration file
    Find the appsettings.json or appsettings.production.json file in the Kavita configuration directory (typically in the same directory as the Kavita executable or in a config subdirectory).
    Affected if The configuration file exists and the installation version is below 0.9.0
  3. Inspect the ReaderController endpoint configuration
    Examine the Kavita web application binaries or source code to confirm the ReaderController.GetImage endpoint is decorated with [AllowAnonymous]. If you have access to decompiled code or the source, verify this attribute is present on the GetImage method.
    Affected if The [AllowAnonymous] attribute is present on the GetImage endpoint in the ReaderController
  4. Test unauthenticated access to the GetImage endpoint
    Using a web browser or curl, attempt to access the GetImage endpoint directly without providing any authentication credentials. Construct a request to an endpoint similar to /api/reader/image?seriesId=1&chapterId=1&page=1 without any Authorization header or valid API key.
    Affected if The request returns image content without requiring authentication or valid API key validation
  5. Verify API key validation is not enforced
    Send a request to the GetImage endpoint with an arbitrary or invalid apiKey parameter (e.g., /api/reader/image?apiKey=invalid). Confirm that the image is still served despite the invalid key.
    Affected if Invalid or missing API keys are accepted and image content is returned

A user is affected if running Kavita version 0.9.0 or earlier where the GetImage endpoint permits unauthenticated access and does not validate the provided API key.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Kavita to version 0.9.0 or later, which removes the [AllowAnonymous] attribute and properly implements authentication validation on the GetImage endpoint.

Recommended fix High confidence

0.9.0

  1. 1. Back up the current Kavita installation and database before upgrading
  2. 2. Upgrade Kavita to version 0.9.0 or later (the fixed release)
  3. 3. Verify the upgrade completed successfully
  4. 4. Confirm the ReaderController.GetImage endpoint now requires authentication by attempting an unauthenticated request

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44775 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44775 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data