CVE-2026-119597

OpenDeepWiki through 2.0.6 Hard-coded JWT Signing Key Admin Token Forgery

Published Oct 30, 2026 CVSS 4.0 · 9.3 Critical EPSS < 1% KEV · Not listed
Description
OpenDeepWiki through 2.0.6 contains a hard-coded JWT signing key vulnerability that allows unauthenticated attackers to forge administrator tokens using the publicly known Jwt:SecretKey in appsettings.json. Attackers can mint HS256 bearer tokens with an Admin role claim to access /api/admin endpoints and control users, roles, repositories, settings, and API keys.

Analysis

AI-generated

Technical impact

OpenDeepWiki versions up to 2.0.6 embed a constant JWT signing key in the configuration file. Because the key is publicly known, an unauthenticated attacker can generate a HS256 bearer token that claims the Admin role. The forged token can be used against the /api/admin endpoints, allowing the attacker to create, modify, and delete users, roles, repositories, settings, and API keys. This grants full administrative control over the application and can lead to data loss, manipulation, or further exploitation of the host system.

Affected Systems

The vulnerability affects AIDotNet’s OpenDeepWiki up to and including version 2.0.6. The hard‑coded key resides in the appsettings.json file and the fault is present in the Program.cs assembly used by all releases prior to 2.0.7.

Risk and Exploitability

The CVSS score of 9.3 classifies this flaw as critical. The EPSS score is not available, but because the attack requires no credentials and only the publicly known key, the likelihood of exploitation is high. The flaw is not listed in CISA’s KEV catalog. An attacker can obtain an admin token by constructing a JWT, then send HTTP requests to privileged API endpoints and fully control the application.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade OpenDeepWiki to version 2.0.7 or later, where the hard‑coded JWT signing key has been removed.
  • If an upgrade is not immediately possible, edit the appsettings.json file to replace the public Jwt:SecretKey with a unique, strong random string and restart the application.
  • After making the change, confirm that previously forged admin tokens are rejected by attempting to access /api/admin endpoints and verifying that the server responds with unauthorized errors.

Generated by OpenCVE AI on October 30, 2026 at 14:55 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Aidotnet
Aidotnet opendeepwiki
Vendors & Products Aidotnet
Aidotnet opendeepwiki
Type Values Removed Values Added
Description OpenDeepWiki through 2.0.6 contains a hard-coded JWT signing key vulnerability that allows unauthenticated attackers to forge administrator tokens using the publicly known Jwt:SecretKey in appsettings.json. Attackers can mint HS256 bearer tokens with an Admin role claim to access /api/admin endpoints and control users, roles, repositories, settings, and API keys.
Title OpenDeepWiki through 2.0.6 Hard-coded JWT Signing Key Admin Token Forgery
Weaknesses CWE-321
References
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 9.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-321

    Use of Hard-coded Cryptographic Key

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Nov 5, 2026, 9:27 PM
Reserved
Oct 30, 2026, 11:46 AM
Status
Deferred
Published
Oct 30, 2026, 2:16 PM
Modified
Nov 5, 2026, 10:17 PM