Kurrent-io KurrentDB 26.1.0 Secondary Indexing improper authorization

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Kurrent-io KurrentDB 26.1.0. This issue affects some unknown processing of the component Secondary Indexing. This manipulation causes improper authorization. This vulnerability is tracked as CVE-2026-81190. The attack is possible to be carried out remotely. No exploit exists. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic was found in Kurrent-io KurrentDB 26.1.0. Affected by this vulnerability is an unknown functionality of the component Secondary Indexing. The manipulation with an unknown input leads to a improper authorization vulnerability. The CWE definition for the vulnerability is CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect confidentiality. The summary by CVE is:

KurrentDB is a database engineered for modern software applications and event-driven architectures. In version 26.1.0, a user authorized to read the $all stream can use Secondary Indexing query capabilities to read arbitrary files accessible to the database process, enumerate directories, and issue HTTP GET requests from that process. The default configuration limits this privilege to administrators. The flaw does not permit file writes and does not expose environment variables. This issue is fixed in version 26.1.1.

The advisory is shared at github.com. This vulnerability is known as CVE-2026-81190 since 08/26/2026. The exploitation appears to be easy. The attack can be launched remotely. Additional levels of successful authentication are required for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1548.002 for this issue.

Upgrading to version 26.1.1 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• Kurrent-io

Name

• KurrentDB

Version

• 26.1.0

Website

• Product: https://github.com/kurrent-io/KurrentDB/

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion