CVE-2026-67343
ArcadeDB cluster token exposure allows root impersonation via management API.
Is CVE-2026-67343 being exploited?
Not confirmed. CVE-2026-67343 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.30% probability of exploitation in the next 30 days.
How severe is CVE-2026-67343?
CVE-2026-67343 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-67343?
Yes. A fix has been recorded for CVE-2026-67343. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-67343 affect?
CVE-2026-67343 affects ArcadeDB < 26.7.2, GET /api/v1/server endpoint, arcadedb.ha.clusterToken, X-ArcadeDB-Cluster-Token header. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-67343?
Upgrade to 26.7.2, rotate cluster tokens, restrict and monitor management API access.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated users can read cluster token and impersonate root to create users, modify/delete databases, and shut down servers.
Immediate action required
- affected< 26.7.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.