CVE-2026-67340
Authenticated schema update allows JS trigger to execute OS commands in ArcadeDB.
Is CVE-2026-67340 being exploited?
Not confirmed. CVE-2026-67340 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.60% probability of exploitation in the next 30 days.
How severe is CVE-2026-67340?
CVE-2026-67340 is rated Critical with a CVSS score of 9.3. 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-67340?
Yes. A fix has been recorded for CVE-2026-67340. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-67340 affect?
CVE-2026-67340 affects ArcadeDB (arcadedb-engine) < 26.7.2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-67340?
Upgrade arcadedb-engine to 26.7.2; restrict UPDATE_SCHEMA and review triggers.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
An authenticated user with UPDATE_SCHEMA can create a JS trigger that calls java.lang.Runtime.exec()/ProcessBuilder, achieving OS command execution when the trigger fires.
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.