---
id: "CVE-2026-41582"
kind: "vulnerability"
aliases: ["CVE-2026-41582"]
title: "Countly server: unauthenticated path traversal reads arbitrary server files"
severity: "high"
cvss: 7.5
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["analytics", "countly", "node.js", "package", "self-hosted"]
not_affected_if: ["external-storage-backend", "managed-hosting", "patched-version"]
published_at: "2026-10-16T16:17:23+00:00"
first_seen_at: "2026-10-23T21:57:13+00:00"
updated_at: "2026-10-25T03:25:06+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-41582", "first_seen_at": "2026-10-23T21:57:13+00:00"}]
---

# Countly server: unauthenticated path traversal reads arbitrary server files

Countly's public image and screenshot routes concatenate user-supplied wildcard paths without containment checks, so on local filesystem storage an unauthenticated request can escape the asset directory. An attacker can read arbitrary files the Countly process can access.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed countly-server version against `24.05.50` and `25.03.44`.
- Confirm the deployment uses the local filesystem backend for assets rather than external storage.
- Test whether `/appimages/../../../../etc/passwd` or a similar path is returned by the server (run only against systems you own).

## Fix

- Upgrade countly-server to `24.05.50` or `25.03.44`, whichever matches your release line.
- Until patched, restrict public access to the affected routes at the reverse proxy.

## Timeline

- 2026-10-23T21:57:13+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-41582

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_