CVE-2026-108860

BotSharp through 5.2.0 Authentication Bypass via Hard-Coded JWT Signing Key

Published Oct 11, 2026 CVSS 4.0 · 9.3 Critical EPSS < 1% KEV · Not listed
Description
BotSharp through 5.2.0 contains an authentication bypass vulnerability that allows unauthenticated remote attackers to forge bearer tokens using the hard-coded Jwt:Key in WebStarter appsettings.json. Attackers can sign tokens with the committed HMAC secret and fixed botsharp issuer and audience to impersonate any known user, including administrators, on Authorize-protected API routes.

Analysis

AI-generated

Technical impact

Blindly using a hard‑coded JWT signing key in BotSharp allows an attacker to forge bearer tokens. By signing the token with the known HMAC secret, the attacker can create a valid token that impersonates any user, including administrators, and bypasses authentication on protected API routes. This is a classic authentication bypass that can lead to privilege escalation, listed as CWE‑321.

Affected Systems

The vulnerability affects BotSharp versions up to and including 5.2.0 from SciSharp. The hard‑coded key is stored in the WebStarter appsettings.json file, and the issuer and audience are fixed, enabling token forgery for any known user.

Risk and Exploitability

The CVSS score of 9.3 marks it as Critical, with a high exploitation risk. The EPSS is not available, and it is not listed in the CISA KEV catalogue. An unauthenticated remote attacker can fabricate a signed JWT and immediately impersonate privileged users, making this vulnerability exploitable via remote web interfaces that accept bearer tokens.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade BotSharp to the latest release that removes the hard‑coded JWT key and introduces secure key management.
  • If an upgrade is not feasible, replace the hard‑coded key in appsettings.json with a strong, randomly generated secret and ensure the issuer and audience are not publicly documented.
  • Enable detailed logging of authentication attempts and monitor for unexpected bearer tokens to detect attempted privilege escalation.

Generated by OpenCVE AI on October 11, 2026 at 15:41 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': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Scisharp
Scisharp botsharp
Vendors & Products Scisharp
Scisharp botsharp
Type Values Removed Values Added
Description BotSharp through 5.2.0 contains an authentication bypass vulnerability that allows unauthenticated remote attackers to forge bearer tokens using the hard-coded Jwt:Key in WebStarter appsettings.json. Attackers can sign tokens with the committed HMAC secret and fixed botsharp issuer and audience to impersonate any known user, including administrators, on Authorize-protected API routes.
Title BotSharp through 5.2.0 Authentication Bypass via Hard-Coded JWT Signing Key
Weaknesses CWE-321
References
Metrics cvssV3_1

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

cvssV4_0

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

Weaknesses
  • CWE-321

    Use of Hard-coded Cryptographic Key

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 14, 2026, 4:47 PM
Reserved
Oct 11, 2026, 1:12 PM
Status
Deferred
Published
Oct 11, 2026, 2:17 PM
Modified
Oct 16, 2026, 7:18 PM