CVE-2026-108860

waiting for further signalsZero needs more public information before it can validate it.

GHSA-w9f8-hvcg-hgcm ↗EUVD-2026-97011 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
SciSharp BotSharp <= 5.2.0
CWE-321 Use of Hard-coded Cryptographic Key
ETK-2026-1248Zero's internal tracking ID, independent of the CVE number., permanent identifier
9d 14h 28msince last run
1h 19mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h53m
0
+4h
+6h
+8h
+10h
+12h

description

BotSharp through 5.2.0 uses a distributed JWT signing secret that can allow unauthenticated remote attackers to mint bearer tokens. An attacker who knows a valid account identity may impersonate that user, including an administrator, on API endpoints protected by authorization checks.

mitigation

Immediately replace the default JWT signing secret with a unique private value and invalidate tokens signed with the old value. Restrict external access to protected API routes until an upstream fixed release is available.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.48%39th percentile
agent run time
1h 19m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-11 13:26Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-11 13:26Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-108860

{
  "etk_id": "ETK-2026-1248",
  "cve_id": "CVE-2026-108860",
  "display_id": "CVE-2026-108860",
  "ghsa_id": "GHSA-w9f8-hvcg-hgcm",
  "euvd_id": "EUVD-2026-97011",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authentication bypass via exposed signing key in BotSharp",
  "summary": "BotSharp through 5.2.0 uses a distributed JWT signing secret that can allow unauthenticated remote attackers to mint bearer tokens. An attacker who knows a valid account identity may impersonate that user, including an administrator, on API endpoints protected by authorization checks.",
  "mitigation": "Immediately replace the default JWT signing secret with a unique private value and invalidate tokens signed with the old value. Restrict external access to protected API routes until an upstream fixed release is available.",
  "vendor": "SciSharp",
  "product": "BotSharp",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 5.2.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "BotSharp",
      "purl": null
    }
  ],
  "cwes": [
    321
  ],
  "cvss_score": 9.3,
  "cvss_src": "cna_vendor",
  "cvss_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",
  "epss_score": 0.0048,
  "epss_percentile": 0.3987,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 79.02367873333333,
  "t0_at": "2026-10-11T13:26:07.369000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-11T13:26:07.369000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-11T13:26:07.369000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-108860"
    }
  }
}

published 2026-10-11 14:00Z
last change 2026-10-21 04:45Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.