Quick answers
- Is CVE-2026-114057 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-114057 being exploited in the wild.
- How severe is CVE-2026-114057?
- Medium severity, with a CVSS score of 4.3, published 21 October 2026.
- Which products and versions are affected?
- ArcadeData ArcadeDB 26.2.1 before 26.10.1.
- Is there a fix for CVE-2026-114057?
- Yes: fixed in 26.10.1. Until then: Restrict network access to the Bolt port (7687) to trusted clients only by configuring firewall rules or binding BOLT_HOST to a non-default interface. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-114057 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-114057?
- Check whether you run ArcadeData ArcadeDB at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 26.10.1
Restrict network access to the Bolt port (7687) to trusted clients only by configuring firewall rules or binding BOLT_HOST to a non-default interface.
Technical details
The Bolt protocol handler's SHOW DATABASES command returns the unfiltered server database list without per-user authorization checks, whereas the HTTP and gRPC handlers correctly apply filterAuthorizedDatabases(). An authenticated attacker with valid credentials for any single database can connect to the Bolt endpoint and enumerate all database names. The vulnerability requires valid credentials (PR:L) and network access to the Bolt port (default 7687), with confidentiality impact limited to metadata exposure only.
Affected products
- ArcadeData ArcadeDB 26.2.1 before 26.10.1
Timeline
- 2026-10-05: disclosed
- 2026-10-21: advisory