dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-47202

CRITICAL · 9.3 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 →
100/100
Remediation priority · Urgent
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.2, an Improper Token validation flaw permits a remote and unauthenticated threat actor to request a JWT for any user including admins given knowledge of their username. This vulnerability is fixed in 0.9.0.2.

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

Kavita versions prior to 0.9.0.2 contain an improper JWT token validation flaw that allows unauthenticated remote attackers to forge JWT tokens for any user, including administrators, simply by knowing the target's username. This grants the attacker full authenticated access to the application with the compromised user's privileges.

MitigationUpgrade Kavita to version 0.9.0.2 or later to remediate this vulnerability. Consider reviewing access logs for suspicious token generation activity and invalidating existing sessions as a precautionary measure.

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:H/VI:H/VA:L/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
    Locate the Kavita application on the system. Check for the Kavita service process, installation directory, or Docker container. Common paths include /opt/kavita, AppData folders on Windows, or the docker image 'kizaing/kavita'.
    Affected if Kavita software is present on the system
  2. Determine installed Kavita version
    Check the version of the installed Kavita instance. If using the web UI, navigate to About or Settings page to view the version number. If using Docker, run 'docker ps' and inspect labels, or check the container logs for version info. If running as a service, check the executable or assembly version.
    Affected if The installed version is lower than 0.9.0.2
  3. Verify network exposure
    Determine if the Kavita instance is accessible over the network. Check firewall rules, reverse proxy configurations, or Docker port mappings (default port 5000) to see if the application is exposed to non-local network access.
    Affected if Kavita is reachable from network addresses beyond localhost, enabling remote exploitation
  4. Confirm JWT authentication is enabled
    Verify that JWT-based authentication is the active authentication mechanism for the Kavita instance. This is the default configuration in affected versions. No specific configuration check is required as this is the default authentication method.
    Affected if JWT authentication is in use (default state for affected versions)

A user is affected if they are running any version of Kavita prior to 0.9.0.2 that is accessible over a network, as an attacker can forge JWT tokens for any user account without authentication.

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.2 or later to remediate this vulnerability. Consider reviewing access logs for suspicious token generation activity and invalidating existing sessions as a precautionary measure.

Recommended fix High confidence

Upgrade to Kavita version 0.9.0.2

  1. 1. Back up your Kavita configuration and database before proceeding with any upgrade
  2. 2. Identify your current Kavita version (check the UI under 'About' or check the Docker tag/container version)
  3. 3. If running via Docker: Stop the Kavita container, pull the version 0.9.0.2 image, and restart the container with your existing configuration
  4. 4. If running via binary/Windows service: Download Kavita 0.9.0.2 from the official releases, stop the service, replace the binary, and restart the service
  5. 5. Verify the upgrade was successful by checking the version number in the UI under 'About'
  6. 6. Since this vulnerability allows JWT token forgery, consider invalidating all existing user sessions or forcing password resets for admin accounts as a precautionary measure

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47202 — 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-47202 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