AIDotNet OpenDeepWiki up to 2.0.6 JWT Signing Key appsettings.json hard-coded credentials

Summaryinfo

A vulnerability was found in AIDotNet OpenDeepWiki up to 2.0.6. It has been classified as critical. This vulnerability affects unknown code of the file appsettings.json of the component JWT Signing Key. This manipulation causes hard-coded credentials. This vulnerability is handled as CVE-2026-119597. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in AIDotNet OpenDeepWiki up to 2.0.6. It has been declared as critical. Affected by this vulnerability is an unknown code block of the file appsettings.json of the component JWT Signing Key. The manipulation with an unknown input leads to a hard-coded credentials vulnerability. The CWE definition for the vulnerability is CWE-798. The product contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-119597 since 10/30/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/30/2026). The attack technique deployed by this issue is T1110.001 according to MITRE ATT&CK.

By approaching the search of inurl:appsettings.json it is possible to find vulnerable targets with Google Hacking.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• Content Management System

Vendor

• AIDotNet

Name

• OpenDeepWiki

Version

• 2.0.0
• 2.0.1
• 2.0.2
• 2.0.3
• 2.0.4
• 2.0.5
• 2.0.6

Website

• Product: https://github.com/AIDotNet/OpenDeepWiki/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion