Skip to main content

Sharkord EUVDEUVD-2026-105161

| CVE-2026-113595 MEDIUM
Missing Authorization (CWE-862)
2026-10-20 VulnCheck GHSA-vc4m-r96v-v753
5.3
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as low-privilege member
  2. Exploit
    Invoke others.changeLogo tRPC mutation
  3. Execution
    Missing MANAGE_SETTINGS check bypassed
  4. Impact
    Replace and broadcast server logo to all clients

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

The attacker must be an authenticated member of a Sharkord server running a version before 0.0.26; no MANAGE_SETTINGS (admin/settings) permission is required because the others.changeLogo tRPC route omits the authorization check present on other settings operations. The exploitation is limited to the integrity of the server logo - the mutation only replaces the logo image broadcast to clients, with no file-system, data-confidentiality, or availability impact. Limiting factors: a valid low-privilege account on the target instance is required (PR:L), so fully unauthenticated attackers and non-members cannot exploit it; affected default behavior is present in v0.0.25 and earlier with no special non-default configuration needed.

Impact

This is a genuine but low-severity authorization flaw (CWE-862), not a high-priority emergency. The provided CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) and the CVSS 5.3 score agree that exploitation is network-reachable, low-complexity, and requires only low-privilege authentication (PR:L) with no user interaction - consistent with 'any authenticated member' in the description. The only impact is integrity-limited (VI:L); confidentiality and availability are explicitly rated None, matching the real-world effect (an unauthorized logo change broadcast to connected clients), so this is a defacement/integrity issue rather than a system-compromise vector. No EPSS score, no CISA KEV listing, and no public exploit code were provided; the source-code commit diff and a test case are available, which disclose the fix but do not constitute a weaponized exploit. There is no signal (KEV/EPSS/POC) suggesting active or widespread exploitation, so this reads as a legitimately fixed low-risk authorization bug rather than an urgent threat. Note: the input Tag 'Authentication Bypass' conflicts with the CWE-862 (missing authorization) classification and the description - this is missing authorization for an already-authenticated user, not an authentication bypass.

Exploit ScenarioDerived

An authenticated low-privilege member of a Sharkord server (one without the MANAGE_SETTINGS permission) directly invokes the others.changeLogo tRPC mutation, which in v0.0.25 and earlier omits the permission check. The attacker removes the owner's logo and uploads a replacement image that is then published to every connected client, defacing the server for all members. No public exploit code was identified at time of analysis, though the patch commit and a regression test disclosing the vulnerable route are publicly available.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 20, 2026

Sharkord before 0.0.26 allows any authenticated server member to replace or remove the server logo without MANAGE_SETTINGS permission because the others.changeLogo tRPC mutation omits its permission check. The impact is limited to integrity of a server setting: the changed logo is published to every connected client, but there is no confidentiality or availability impact and the attacker must already hold a valid low-privilege account. No public exploit code was identified at time of analysis, and a vendor-released fix is available in Sharkord 0.0.26.

RemediationAI

Upgrade to Sharkord 0.0.26 or later; the vendor-released patch version 0.0.26 contains commit fd15061eaf366c7150325780a2d7b4b452f1134f and the fix release is at https://github.com/Sharkord/sharkord/releases/tag/v0.0.26. Review the VulnCheck advisory and GitHub issues #387/#851 for vendor details. If immediate upgrade is not possible, restrict server membership and invitations to trusted users and monitor/restore unauthorized logo changes, understanding that this only reduces exposure because the missing MANAGE_SETTINGS check remains; another compensating control is to block or restrict the others.changeLogo tRPC route at a reverse proxy, but that can break legitimate logo updates from administrators and is not a substitute for patching.

Affected VersionsENISA

sharkord 0 <0.0.26

Affected Packages

euvd sharkord fix: 0.0.26

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Sharkord is a self-hosted collaboration/chat server whose server API is built on tRPC. The vulnerable mutation in apps/server/src/routers/others/change-logo.ts uses protectedProcedure, which confirms the caller is authenticated, but it does not invoke ctx.needsPermission(Permission.MANAGE_SETTINGS) before accepting a temp file ID and updating the logo. This is CWE-862 (missing authorization): the route enforces authentication but not the role/permission required for a settings-changing action. The upstream commit fd15061 adds the Permission import and the needsPermission call and adds a regression test showing a second non-admin user is rejected with 'Insufficient permissions' while the original logo remains. CPE cpe:2.3:a:sharkord:sharkord:*:*:*:*:*:*:*:* covers the affected pre-0.0.26 product line; CVSS PR:L reflects that a valid member account is required, and there is no confidentiality or availability impact beyond limited integrity of the displayed logo.

Know when Sharkord gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 5.3 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
vuln.today AI 4.3 MEDIUM

Network-reachable tRPC route, low complexity, requires an authenticated low-privilege member (PR:L); only the logo is altered so I:L with C:N/A:N and no scope change.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
Low
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

Sharkord before 0.0.26 contains a missing authorization vulnerability in the others.changeLogo tRPC mutation that allows any authenticated member to modify the server logo without the MANAGE_SETTINGS permission. Attackers can remove the current logo and replace it with an uploaded image that is published to every connected client.

Threat Intelligence Overview

EPSS Score
0.3%
Top 83% exploitable
Prevalence
Low
niche self-hosted open-source chat/community server, limited production footprint
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy