CVE-2026-67341: ArcadeDB vulnerability
CVE-2026-67341 affects ArcadeDB. Attackers with database access can execute arbitrary JavaScript code by submitting DEFINE FUNCTION statements, bypassing security controls intended to restrict scripting to administrators.
What happened
2 fail to enforce scripting authorization checks on the SQL DEFINE FUNCTION statement with LANGUAGE js. A security weakness in ArcadeDB is being tracked as CVE-2026-67341. CVE-2026-67341 affects ArcadeDB.
Attackers with database access can execute arbitrary JavaScript code by submitting DEFINE FUNCTION statements, bypassing security controls intended to restrict scripting to administrators. The important point is that running an affected version of ArcadeDB creates exposure, while an actual compromise still depends on whether the attacker can reach the trigger conditions described above. ArcadeDB versions before 26.
No exploitation flag is present in the retained CyberDeltaForce data at this time; that status can change as vendor and threat-intelligence reporting develops.
Editorial note: this News Brief follows the available evidence and adds length only when additional facts or useful context are available. Where public reporting does not establish a specific victim sequence, CyberDeltaForce does not present one as fact.
What the reporting and advisory establish
ArcadeDB versions before 26.
2 fail to enforce scripting authorization checks on the SQL DEFINE FUNCTION statement with LANGUAGE js.
No exploitation flag is present in the retained CyberDeltaForce data at this time; that status can change as vendor and threat-intelligence reporting develops.
A security weakness in ArcadeDB is being tracked as CVE-2026-67341. Attackers with database access can execute arbitrary JavaScript code by submitting DEFINE FUNCTION statements, bypassing security controls intended to restrict scripting to administrators. The issue currently carries a CRITICAL 9.8 severity signal in the available reporting. There is no reported exploitation in the current available reporting, so the public picture at this point is a disclosed vulnerability with known exploitation conditions rather than a confirmed compromise of every affected installation. The important point is that running an affected version of ArcadeDB creates exposure, while an actual compromise still depends on whether the attacker can reach the trigger conditions described above. ArcadeDB versions before 26.
What this means for your environment
Move from the published facts to the technical path, exposure conditions and defensive decisions that matter in a real environment.
Attack & Exploitation Path
The sequence below shows how the vulnerability can be reached and what successful exploitation can produce. Each stage is labeled by evidence status.
Required condition: ArcadeDB is present and the vulnerable function is reachable in the way the software is normally used.
Required condition: attacker-controlled input or the relevant workflow reaches the affected code path.
Not publicly disclosed in enough technical detail to describe the mechanism without inference.
Not publicly disclosed in enough detail to state a specific post-exploitation result without inference.
Map ArcadeDB to real assets, verify the vendor fix or mitigation, confirm the vulnerable path is no longer reachable, and review relevant telemetry for behavior consistent with exploitation.
Why this matters to you
CVE-2026-67341 matters because the practical risk is not the score alone — it is whether ArcadeDB before 26 exists in your environment and whether the reported trigger or exposure path can reach it. The current severity is CRITICAL 9.8. No exploitation flag is currently present in the CDF data, but that does not remove the need to validate affected systems.
Does this deserve attention in my environment?
Check the conditions below against your use of ArcadeDB before 26.
Select the conditions that are true in your environment. Leaving a condition unselected does not mean you are safe — it only means you have not marked it as applicable.
- Search endpoint, software and asset inventory for ArcadeDB before 26.
- Confirm the vendor-recommended fixed version or mitigation and verify deployment, not just assignment, across affected assets.
- Review relevant endpoint, application, network or identity telemetry for activity associated with exploitation of the affected component.
- Track vendor and government guidance for any change in exploitation status while remediation is underway.
What remains unconfirmed
- Available reporting does not currently indicate exploitation, but that can change as vendor, government or threat-intelligence reporting develops.
Sources & References
Original reporting and technical references are kept here for readers who want to verify the facts. Publisher names stay out of the reading flow above.