Countly countly-server up to 24.05.49/25.03.43 Local Filesystem Backend frontend/express/app.js getStats/getStream information disclosure

Summaryinfo

A vulnerability was found in Countly countly-server up to 24.05.49/25.03.43. It has been rated as problematic. This issue affects the function getStats/getStream of the file frontend/express/app.js of the component Local Filesystem Backend. The manipulation leads to information disclosure. This vulnerability is uniquely identified as CVE-2026-41582. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is advised.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in Countly countly-server up to 24.05.49/25.03.43. This issue affects the function getStats/getStream of the file frontend/express/app.js of the component Local Filesystem Backend. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:

countly-server is the server-side part of Countly, a product analytics solution. Prior to 24.05.50 and 25.03.44, public image and screenshot routes implemented in frontend/express/app.js, plugins/star-rating/frontend/app.js, and plugins/dashboards/frontend/app.js concatenate attacker-controlled wildcard paths without containment validation. On deployments using the local filesystem backend, an unauthenticated request can traverse outside the intended asset directories and reach getStats or getStream in api/utils/countlyFs.js, allowing arbitrary readable server files to be disclosed. The affected routes include /appimages/*, /memberimages/*, */screenshots/*, /star-rating/images/*, and /dashboards/images/screenshots/*. This issue is fixed in versions 24.05.50 and 25.03.44.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-41582 since 04/21/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

Upgrading to version 24.05.50 or 25.03.44 eliminates this vulnerability.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• Countly

Name

• countly-server

Version

• 24.05.0
• 24.05.1
• 24.05.2
• 24.05.3
• 24.05.4
• 24.05.5
• 24.05.6
• 24.05.7
• 24.05.8
• 24.05.9
• 24.05.10
• 24.05.11
• 24.05.12
• 24.05.13
• 24.05.14
• 24.05.15
• 24.05.16
• 24.05.17
• 24.05.18
• 24.05.19
• 24.05.20
• 24.05.21
• 24.05.22
• 24.05.23
• 24.05.24
• 24.05.25
• 24.05.26
• 24.05.27
• 24.05.28
• 24.05.29
• 24.05.30
• 24.05.31
• 24.05.32
• 24.05.33
• 24.05.34
• 24.05.35
• 24.05.36
• 24.05.37
• 24.05.38
• 24.05.39
• 24.05.40
• 24.05.41
• 24.05.42
• 24.05.43
• 24.05.44
• 24.05.45
• 24.05.46
• 24.05.47
• 24.05.48
• 24.05.49
• 25.03.0
• 25.03.1
• 25.03.2
• 25.03.3
• 25.03.4
• 25.03.5
• 25.03.6
• 25.03.7
• 25.03.8
• 25.03.9
• 25.03.10
• 25.03.11
• 25.03.12
• 25.03.13
• 25.03.14
• 25.03.15
• 25.03.16
• 25.03.17
• 25.03.18
• 25.03.19
• 25.03.20
• 25.03.21
• 25.03.22
• 25.03.23
• 25.03.24
• 25.03.25
• 25.03.26
• 25.03.27
• 25.03.28
• 25.03.29
• 25.03.30
• 25.03.31
• 25.03.32
• 25.03.33
• 25.03.34
• 25.03.35
• 25.03.36
• 25.03.37
• 25.03.38
• 25.03.39
• 25.03.40
• 25.03.41
• 25.03.42
• 25.03.43

Website

• Product: https://github.com/Countly/countly-server/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion