Cpe:2.3:a:botsharp:botsharp:*:*:*:*:*:*:*:* - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/cpes/cpe2.3abotsharpbotsharp/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioSun, 11 Oct 2026 16:02:34 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgAuthentication Bypass in BotSharp via Hard-Coded JWT Secrethttps://feed.craftedsignal.io/briefs/2026-10-botsharp-auth-bypass/Sun, 11 Oct 2026 16:02:34 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-10-botsharp-auth-bypass/BotSharp versions 5.2.0 and earlier contain an authentication bypass vulnerability allowing unauthenticated attackers to forge administrative bearer tokens using a hard-coded JWT signing key.BotSharp versions 5.2.0 and earlier are affected by a critical authentication bypass vulnerability (CVE-2026-108860). The flaw resides in the WebStarter component, where a hard-coded HMAC secret key is defined within the appsettings.json file for JWT signing. This static secret, combined with predictable issuer and audience fields, permits unauthenticated remote attackers to generate valid, signed JSON Web Tokens (JWTs). By successfully forging these tokens, an attacker can impersonate any user, including accounts with administrative privileges, to bypass authorization controls on API endpoints. This vulnerability significantly impacts the confidentiality and integrity of any organization deploying BotSharp, as it allows for full unauthorized access to protected API routes without requiring valid credentials.

Impact

The vulnerability allows for complete compromise of the BotSharp application instance. Success grants attackers the ability to access, modify, or delete data through restricted API routes. There is no specific sector targeting mentioned, but any environment utilizing BotSharp as an agent orchestration framework is susceptible to full administrative takeover.

Recommendation

Prioritized, concrete actions for detection engineering teams:

  • Update BotSharp deployments to a version that patches CVE-2026-108860 by removing hard-coded secrets from the configuration.
  • Audit all BotSharp appsettings.json files for the existence of hard-coded JWT signing keys.
  • Implement monitoring for anomalous or high-volume administrative actions originating from API requests, focusing on tokens with unexpected issuer or audience claims.
  • Rotate all secrets and credentials used within the BotSharp environment, as the existing hard-coded key must be considered compromised.
]]>criticaladvisory