Quick answers
- Is CVE-2026-93593 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93593 being exploited in the wild.
- How severe is CVE-2026-93593?
- High severity, with a CVSS score of 8.1, published 18 September 2026.
- Which products and versions are affected?
- ArcadeData ArcadeDB before 26.9.1.
- Is there a fix for CVE-2026-93593?
- A patch was published on 2026-09-18: Fixed in version 26.9.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-93593 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-93593?
- 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
ArcadeDB's ACL enforcement mechanism has a critical flaw in its authorization resolver for TimeSeries types. The vulnerability stems from ServerSecurityDatabaseUser.updateFileAccess() building permission maps indexed by file/bucket ID and calling getInvolvedTypeByBucketId() to resolve permissions. TimeSeries types do not own normal record buckets, causing this lookup to return null and the ACL entries to be silently skipped. Consequently, access control checks fail open, allowing reads and writes that should be denied. The flaw affects both explicit deny rules for specific TimeSeries types and bundled default security groups (readonly and catch-all policies). An authenticated attacker with low privileges can exploit this by performing SQL queries and inserts on restricted TimeSeries types that should be blocked. The vulnerability was confirmed patched in ArcadeDB 26.9.1.
Affected products
- ArcadeData ArcadeDB before 26.9.1
Timeline
- 2026-09-18: disclosed
- 2026-09-18: patched: Fixed in version 26.9.1