CVE-2026-81190kurrent-io KurrentDB external control of a file name
CVE-2026-81190 is a external control of a file name in kurrent-io KurrentDB, rated medium (6.9 on CVSS 4.0).
Why this priority: Medium severity, with no exploitation signal.
Published · Updated · NVD status: Received
What it is
Input decides which file the software opens, so a caller can point it elsewhere. The server can be made to fetch an address of the attacker's choosing, including internal services and cloud metadata endpoints.
How it is reached
An attacker can exploit it over the network, with an administrator account, and nobody has to click anything.
What an attacker gains
A successful attack can read the data it protects. In practice, this kind of flaw lets an attacker read or write files outside the folders the service meant to expose.
Is it being exploited?
There is no public report of exploitation yet.
What to do
- No fixed version is listed yet. Find every place kurrent-io KurrentDB runs, watch the references for a fix, and plan a replacement if it is no longer supported.
- While there is no fix, review who holds accounts that can reach it.
Description from NVD
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.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- File storage the service can read or write. The flaw sits between the application and the file system it can reach.
- Services that fetch URLs or call other hosts for a caller. The flaw sits between the application and the internal network behind it.
Trust boundaries in play
- Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
- Between the application and the file system it can reach. An attacker who crosses it can read or write files outside the folders the service meant to expose.
- Between the application and the internal network behind it. An attacker who crosses it can make the server send requests into internal networks or cloud metadata.
Questions to answer about your own systems
- Where does kurrent-io KurrentDB run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
Read more
Patches and commits
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.