Skip to main content
VulnerabilityPublished

CVE-2026-75839: ArcadeData arcadedb · Information Exposure

Affects ArcadeData arcadedbSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 26.8.1 when convenient.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 26.8.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Aug 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 15 Nov 2026.

What to do

Upgrade ArcadeData arcadedb to 26.8.1.

Affected software

ProductAffectedFixed in
ArcadeDataarcadedbAffected
  • <26.8.1
Fixed in
  • 26.8.1
Mavencom.arcadedb/arcadedb-serverpkg:maven/com.arcadedb/arcadedb-serverOther threatsAffected
  • <=26.7.3
Fixed in–

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

AI-suggested

Upgrade ArcadeDB to version 26.8.1 or later, where this vulnerability is fixed. No other mitigation is indicated or required by the vendor advisory.

Description

ArcadeDB versions up to 26.7.3 have an insecure direct object reference (IDOR) vulnerability in the Raft cluster-info endpoints. This flaw allows any authenticated user on a high-availability cluster to access metadata across all databases, including names, transaction IDs, and cluster topology, without proper authorization. The issue is fixed in version 26.8.1.

References

Community reviews

Loading reviews…