Skip to main content
CVE-2026-134338VulnerabilityPublished

ArcadeDB 25.8.1 before 26.11.1 contains an incorrect authorization vulnerability because per-type ACLs are keyed by

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-134338· High 8.7

Not known to be exploited · CVSS 8.7 High : upgrade to 26.11.1 soon.

Data as of 21 Nov 2026, 19:42 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.7
CNA (VulnCheck)CVSS 3.18.8
Patch
Available – fixed in 26.11.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.

What to do

Upgrade arcadedb to 26.11.1.

Affected software

ProductAffectedFixed in
ArcadeDataarcadedbAffected
  • >=25.8.1 <26.11.1
Fixed in
  • 26.11.1
Mavenarcadedbpkg:maven/arcadedbOther threatsAffected
  • >=25.8.1 <26.11.1
Fixed in
  • 26.11.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in ArcadeDB version 26.11.1 and later. Users should upgrade to version 26.11.1 or newer to remediate this vulnerability. No other mitigation actions are specified.

Description

ArcadeDB versions from 25.8.1 up to but not including 26.11.1 contain an incorrect authorization vulnerability related to per-type ACLs. The issue arises because ACLs are keyed by type name, and renaming types does not update the permission configuration. This allows authenticated users with only updateSchema privileges to rename a denied type and gain unauthorized read, delete, and truncate access. The unauthorized access is immediate for TIMESERIES types and delayed until the next security rebuild for record-backed types.

References

Community reviews

Loading reviews…