---
title: "CVE-2026-108860: BotSharp - Authentication Bypass"
description: "BotSharp through 5.2.0 contains an authentication bypass caused by hard-coded Jwt:Key in WebStarter appsettings.json, letting unauthenticated remote attackers forge bearer tokens to impersonate any user including administrators, exploit requires knowledge of the hard-coded key."
url: https://panop.io/threat-heartbeat/CVE-2026-108860/
---

# CVE-2026-108860 BotSharp - Authentication Bypass

BotSharp through 5.2.0 contains an authentication bypass caused by hard-coded Jwt:Key in WebStarter appsettings.json, letting unauthenticated remote attackers forge bearer tokens to impersonate any user including administrators, exploit requires knowledge of the hard-coded key.

CVSS base score 9.1 /10

Critical

CISA KEV

Not listed

Public exploit

None known

EPSS

0.48% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-108860)

## Details

Type

Authentication Bypass

Impact

Broken Authentication

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Published

11 October 2026

Updated

15 October 2026

Weakness

[CWE-321](https://cwe.mitre.org/data/definitions/321.html)

## Vendor fix

Update to the latest version that removes hard-coded Jwt:Key or rotate the Jwt:Key to a secure secret.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-108860](https://nvd.nist.gov/vuln/detail/CVE-2026-108860)
- [https://hackmd.io/@1ExmmukzRMWN7B4gQ4W-4Q/scisharp-botsharp-public-jwt-signing-key](https://hackmd.io/@1ExmmukzRMWN7B4gQ4W-4Q/scisharp-botsharp-public-jwt-signing-key)
- [https://www.vulncheck.com/advisories/botsharp-through-5.2.0-authentication-bypass-via-hard-coded-jwt-signing-key](https://www.vulncheck.com/advisories/botsharp-through-5.2.0-authentication-bypass-via-hard-coded-jwt-signing-key)
- [https://github.com/SciSharp/BotSharp](https://github.com/SciSharp/BotSharp)
- [https://github.com/SciSharp/BotSharp/blob/a11ee0317cab5c619df1cb5d0c4fc39d1b6e30b4/src/Infrastructure/BotSharp.OpenAPI/BotSharpOpenApiExtensions.cs#L46-L57](https://github.com/SciSharp/BotSharp/blob/a11ee0317cab5c619df1cb5d0c4fc39d1b6e30b4/src/Infrastructure/BotSharp.OpenAPI/BotSharpOpenApiExtensions.cs#L46-L57)
- [https://github.com/SciSharp/BotSharp/blob/a11ee0317cab5c619df1cb5d0c4fc39d1b6e30b4/src/WebStarter/appsettings.json#L16-L20](https://github.com/SciSharp/BotSharp/blob/a11ee0317cab5c619df1cb5d0c4fc39d1b6e30b4/src/WebStarter/appsettings.json#L16-L20)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)
