Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Network-reachable, no auth required per description and CVSS PR:N; AC:L reflects that the FileSystem storage condition is a deployment choice, not an attack-time complexity barrier; C:H for arbitrary file read, no integrity or availability impact.
Primary rating from Vendor (hackerone).
CVSS VectorVendor: hackerone
Lifecycle Timeline
3DescriptionCVE.org
An unauthenticated path traversal (LFI) vulnerability exists under /custom-sounds/ when CustomSounds storage is configured to FileSystem. By including ../ sequences in the request path, an attacker can read arbitrary files outside the base directory.
AnalysisAI
Unauthenticated path traversal in Rocket.Chat's /custom-sounds/ endpoint allows any remote attacker to read arbitrary files from the server filesystem when the CustomSounds feature is configured to use FileSystem storage. By injecting ../ sequences into the request path, an attacker can exfiltrate sensitive server files such as configuration files, private keys, or credential stores outside the intended sound file directory. No public exploit code or CISA KEV listing has been identified at time of analysis, but the unauthenticated network vector and high confidentiality impact (CVSS 7.5) make this a serious risk for self-hosted deployments with FileSystem storage enabled.
Technical ContextAI
Rocket.Chat (cpe:2.3:a:rocket.chat:rocket.chat:*:*:*:*:*:*:*:*) is a widely-used open-source self-hosted team communication platform. The affected endpoint /custom-sounds/ serves user-uploaded audio files and resolves file paths directly on the server's local filesystem when the CustomSounds storage backend is set to FileSystem rather than an object/cloud storage provider (e.g., S3). CWE-22 (Improper Limitation of a Pathname to a Restricted Directory - Path Traversal) arises because user-supplied path components in HTTP requests are not sanitized before being joined to the base directory, allowing traversal sequences such as ../../../../etc/passwd to escape the intended sound file root. The CPE wildcard (*) across all version fields indicates no specific version range has been bounded in available data - all Rocket.Chat versions are potentially in scope. This class of vulnerability is well-understood and trivially exploitable once the precondition (FileSystem storage) is met.
RemediationAI
No vendor-released patch has been identified at time of analysis. Monitor the HackerOne report at https://hackerone.com/reports/3514640 and the Rocket.Chat security advisories channel for a confirmed fix version and apply it as soon as available. As an immediate compensating control, switch the CustomSounds storage backend from FileSystem to an S3-compatible or cloud object storage provider - this eliminates local filesystem path resolution entirely and fully mitigates the vulnerability without functional impact to end users. If FileSystem storage cannot be changed immediately, restrict access to the /custom-sounds/ endpoint at the reverse proxy or WAF layer to trusted IP ranges only; note this will break custom sound delivery for external or remote users. Additionally, ensure the Rocket.Chat server process runs under a dedicated least-privilege OS user with read access scoped only to its required directories, minimizing the files reachable via traversal even if the endpoint is exploited.
More in Rocket Chat
View allA sanitization vulnerability exists in Rocket.Chat server versions <3.13.2, <3.12.4, <3.11.4 that allowed queries to an
A improper input sanitization vulnerability exists in Rocket.Chat server 3.11, 3.12 & 3.13 that could lead to unauthenti
A improper authentication vulnerability exists in Rocket.Chat <v5, <v4.8.2 and <v4.7.5 that allowed two factor authentic
A SQL injection vulnerability exists in Rocket.Chat <v3.18.6, <v4.4.4 and <v4.7.3 which can allow an attacker to retriev
A Server-Side Request Forgery (SSRF) affects Rocket.Chat's Twilio webhook endpoint before version 6.10.1. Rated high sev
Rocket.Chat versions prior to 6.12.0 expose the OAuth applications API endpoint to any authenticated user, allowing disc
An information disclosure vulnerability exists in the Rocket.Chat server fixed v3.13, v3.12.2 & v3.11.3 that allowed ema
An improper authentication vulnerability exists in Rocket.Chat Mobile App <4.14.1.22788 that allowed an attacker with ph
A cleartext transmission of sensitive information exists in Rocket.Chat <v5, <v4.8.2 and <v4.7.5 relating to Oauth token
An information disclosure vulnerability exists in Rocket.Chat <v5 due to the getUserMentionsByChannel meteor server meth
Rocket.Chat is an open-source fully customizable communications platform developed in JavaScript. Rated medium severity
A blind self XSS vulnerability exists in RocketChat LiveChat <v1.9 that could allow an attacker to trick a victim pastin
Same weakness CWE-22 – Path Traversal
View allSame technique Path Traversal
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-52560
GHSA-6c37-9jgq-mgm8