Quick answers
- Is CVE-2026-75854 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-75854 being exploited in the wild.
- How severe is CVE-2026-75854?
- Critical severity, with a CVSS score of 9.8, published 18 August 2026.
- Which products and versions are affected?
- ArcadeData ArcadeDB before 26.8.1.
- Is there a fix for CVE-2026-75854?
- A patch was published on 2026-08-18: version 26.8.1 released with fix Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-75854 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-75854?
- 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.
Technical details
The vulnerability is a missing authentication check (CWE-306) in the RedisNetworkExecutor component of ArcadeDB's Redis wire-protocol plugin. Unlike ArcadeDB's other protocol emulators (Postgres, MongoDB), the Redis handler accepts raw TCP connections on the configured Redis port (default 6379, bound to 0.0.0.0 by default) and processes RESP protocol commands (GET, SET, HSET, HGET, HMGET, HDEL, etc.) without ever calling authentication APIs or validating user credentials. Attackers with network access can connect using any standard Redis client (redis-cli, Jedis) and immediately execute arbitrary read, write, and delete operations against all databases on the server. The fix is available in version 26.8.1 and later, where authentication has been implemented.
Affected products
- ArcadeData ArcadeDB before 26.8.1
Timeline
- 2026-08-04: disclosed
- 2026-08-18: patched: version 26.8.1 released with fix