Zero Radar
← feed
CriticalVulnerabilityCVE-2026-119597updated 30 Oct 2026, 18:25 UTC

OpenDeepWiki admin access can be forged with a publicly known key

OpenDeepWiki uses a secret key to sign login tokens, and that key is written in a public config file. Anyone who reads it can create a fake admin login and take control of the whole system without a password.

Official, 2 sources
SeverityCriticalCVSS 9.3 of 10
Being exploited?UnclearNo reports either way yet
Fix available?UnclearNo fixed version published in the sources yet
How sure is this?Official, 2 sourcesBacked by an official source

How the attack works simplified

  1. 1Attacker reads configKey is public in appsettings.json
  2. 2Forges admin tokenSigns HS256 token with Admin role claim
  3. 3Sends token to serverBearer token on each request
  4. 4Server accepts tokenSignature matches the known key
  5. 5Admin API accessUsers, repos, settings, API keys
  6. ResultAttacker controls the admin functions

What happened

OpenDeepWiki through version 2.0.6 ships a hard-coded JWT signing key (Jwt:SecretKey in appsettings.json). Attackers can mint HS256 bearer tokens with an Admin role claim and use them against /api/admin endpoints.

Why it is dangerous: An unauthenticated attacker can manage users, roles, repositories, settings, and API keys. Any deployment that keeps the default configuration is exposed to full administrative takeover.

Are you affected?

You are affected if you run OpenDeepWiki through version 2.0.6 with the default Jwt:SecretKey value in appsettings.json.

OpenDeepWiki through 2.0.6

What to do

  1. Change Jwt:SecretKey in appsettings.json to a long, random, secret value that is not stored in the public code.
  2. Check your admin users, roles, repositories, and API keys for changes you did not make.
  3. Restrict access to the admin API and the application to trusted networks until the key is changed.

Timeline

  1. 30 Oct 2026, 14:16 UTC
    Publicly disclosed
  2. 30 Oct 2026, 14:16 UTC
    Reported by NVD · NVD
  3. 30 Oct 2026, 14:17 UTC
    Picked up by Zero Radar
  4. 30 Oct 2026, 18:25 UTC
    GitHub Advisory reported on it · GitHub Advisory

Sources 2 reports, oldest first

Official vendor, government CERT or advisory database

Technical details

ID
CVE-2026-119597 · GHSA-fc52-73gp-r537
CVSS
9.3 / 10
EPSS
0.4% chance of exploitation within 30 days
Disclosed
30 Oct 2026, 14:16 UTC
On Zero Radar
30 Oct 2026, 14:17 UTC (1 min after disclosure)
Last change
30 Oct 2026, 18:25 UTC

The plain-language parts and the attack diagram were written by an AI model (anthropic/claude-haiku-5.5) from the sources above. Facts like versions, exploitation and dates come from the sources themselves. How Zero Radar works

OpenDeepWiki admin access can be forged with a publicly known key · Zero Radar