Secuno
ENNL
Book demo

CVE-2026-93593

8.1 HIGH
  1. Published18 Sept 2026

Description

ArcadeDB before 26.9.1 fails to enforce security-group types ACL entries for TimeSeries types because the ACL resolver builds permissions from bucket IDs, but TimeSeries types do not own normal record buckets. An authenticated low-privilege user can read or insert TimeSeries samples despite explicit deny rules by exploiting the missing type-name-based access check that causes permission lookups to fail open.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredLow
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityNone
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-935948.1
ArcadeDB (Maven artifact com.arcadedb:arcadedb-engine) through 26.8.1 enforces its…
CVE-2026-687918.6
Incorrect authorization in Azure Machine Learning allows an unauthorized attacker to…
CVE-2026-928018.8
cc-connect through 1.5.0 fails to enforce per-user allowlist filtering in the…
CVE-2026-927968.8
Manticore Search versions 27.0.0 before 28.4.4 fail to validate permissions for all…
CVE-2026-927938.1
GoAdmin through 1.2.26 fails to properly anchor the logout pattern when checking…
CVE-2026-927888.8
Coze Studio through 0.5.1 fails to validate that table names in workflow SQL…

Frequently asked

Is CVE-2026-93593 being actively exploited?

CVE-2026-93593 is not in the CISA KEV catalog.

How severe is CVE-2026-93593?

CVE-2026-93593 has a CVSS 3.1 base score of 8.1, rated high.

How do I fix CVE-2026-93593?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-93593 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.