Skip to main content
VulnerabilityPublished Updated

CVE-2026-67343: ArcadeData arcadedb · Information Exposure

Affects ArcadeData arcadedbSource CVE Database V5

0
Compare

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

Data as of 30 Oct 2026, 20:25 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 26.7.2
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 1 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 30 Oct 2026.

What to do

Upgrade arcadedb and arcadedata/arcadedb to 26.7.2.

Affected software

ProductAffectedFixed in
ArcadeDataarcadedbAffected
  • <26.7.2
Fixed in
  • 26.7.2
GitHubarcadedata/arcadedbpkg:github/arcadedata/arcadedbOther threatsAffected
  • <26.7.2
Fixed in
  • 26.7.2

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.7.2. Users should upgrade to version 26.7.2 or later to remediate this vulnerability. No official vendor advisory or patch link is provided in the data, so users should verify the patch availability from the vendor directly.

Description

ArcadeDB versions before 26.7.2 fail to properly redact the cluster token in the GET /api/v1/server endpoint, allowing authenticated users to retrieve the arcadedb.ha.clusterToken value in cleartext. Attackers can use the leaked token with X-ArcadeDB-Cluster-Token and X-ArcadeDB-Forwarded-User headers to impersonate root and execute administrative actions including user creation, database operations, and server shutdown.

References

Community reviews

Loading reviews…