CVE-2026-119660: yincongcyincong MuseBot · Use of Default Cryptographic Key
Affects yincongcyincong MuseBotSource CVE Database V5
Not known to be exploited · CVSS 9.3 Critical : upgrade to 2.0.0 as a priority.
Data as of 30 Oct 2026, 15:02 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 9.3 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 9.8 |
- Patch
- Available – fixed in 2.0.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 30 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 30 Oct 2026.
What to do
Upgrade yincongcyincong MuseBot to 2.0.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| yincongcyincongMuseBot | Affected
| Fixed in
|
GitHubMuseBotpkg:github/MuseBotOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade MuseBot to version 2.0.0 or later, where the vulnerability is fixed. No other mitigation is required as the fix addresses the root cause by removing the use of the default cryptographic key.
Description
MuseBot versions prior to 2.0.0 contain a critical authentication bypass vulnerability due to the use of a hard-coded default session key. This flaw allows unauthenticated attackers to forge admin sessions by signing session cookies with the default key, granting full administrative access. Exploitation enables attackers to read sensitive data such as password hashes, chat records, and bot configurations, and to stop bots. The vulnerability is fixed in MuseBot version 2.0.0.
References
- github.com/yincongcyincong/MuseBot/issues/61 (opens in a new tab)
- github.com/yincongcyincong/MuseBot/commit/3e64518948fe7037058f07ef987d35216c3f0cae (opens in a new tab)
- github.com/yincongcyincong/MuseBot/commit/139f6158b50283b983d76976f593a3a09a064681 (opens in a new tab)
- github.com/yincongcyincong/MuseBot/blob/v1.0.42/admin/conf/conf.go (opens in a new tab)
- github.com/yincongcyincong/MuseBot/blob/v1.0.42/admin/controller/login.go (opens in a new tab)
- hackmd.io/@hieuPenguinnn/musebot-admin-default-session-key-auth-bypass (opens in a new tab)
- github.com/yincongcyincong/MuseBot (opens in a new tab)
- vulncheck.com/advisories/musebot-before-2.0.0-authentication-bypass-via-hard-coded-session-key (opens in a new tab)