Skip to main content
VulnerabilityPublished Updated

CVE-2026-108860: SciSharp BotSharp · Use of Hard-coded Cryptographic Key

Affects SciSharp BotSharpSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.3 Critical.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
SciSharpBotSharpAffected
  • <=5.2.0
Fixed in–
GitHubBotSharppkg:github/BotSharpOther threatsAffected
  • <=5.2.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, users should consider mitigating risk by changing the hard-coded Jwt:Key to a secure, unique secret and avoiding committing secrets in configuration files. Additionally, restricting access to configuration files and implementing additional authentication layers may reduce exposure.

Description

BotSharp versions up to 5.2.0 contain a critical authentication bypass vulnerability due to a hard-coded cryptographic key. This flaw allows unauthenticated remote attackers to forge bearer tokens by using the fixed Jwt:Key found in the WebStarter appsettings.json file. Exploiting this, attackers can impersonate any user, including administrators, on API routes protected by authorization.

References

Community reviews

Loading reviews…