CVE-2026-113595: sharkord · Missing Authorization
Affects sharkordSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 0.0.26 when convenient.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-10-23.
- Patch
- Available – fixed in 0.0.26
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Upgrade sharkord to 0.0.26.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Sharkordsharkord | Affected
| Fixed in
|
GitHubsharkordpkg:github/sharkordOther 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 Sharkord to version 0.0.26 or later, where this missing authorization vulnerability is fixed. No other mitigation is required as the issue is resolved in the official patch.
Description
CVE-2026-113595 is a missing authorization vulnerability in Sharkord versions before 0.0.26. It affects the others.changeLogo tRPC mutation, allowing any authenticated member to change the server logo without requiring the MANAGE_SETTINGS permission. This enables attackers to remove the existing logo and replace it with an uploaded image visible to all connected clients. The vulnerability has a medium severity with a CVSS score of 5.3 and was fixed in version 0.0.26.
References
- github.com/Sharkord/sharkord/issues/387 (opens in a new tab)
- github.com/Sharkord/sharkord/issues/851 (opens in a new tab)
- github.com/Sharkord/sharkord/commit/fd15061eaf366c7150325780a2d7b4b452f1134f (opens in a new tab)
- github.com/Sharkord/sharkord/releases/tag/v0.0.26 (opens in a new tab)
- github.com/Sharkord/sharkord/blob/v0.0.25/apps/server/src/routers/others/change-logo.ts (opens in a new tab)
- vulncheck.com/advisories/sharkord-before-0.0.26-missing-authorization-via-changelogo-trpc-route (opens in a new tab)