External risk intelligence

ToolJet Cross-Tenant Data Manipulation Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.4)

CVE-2026-82874

ToolJet is a low-code platform commonly deployed as an internet-facing web application or API service. The vulnerability exists in database management endpoints that are accessible to users of the platform. Because the application is typically exposed to the internet to allow remote users to build and access internal tools, the attack surface is considered likely to be internet-reachable.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability in the ToolJet low-code platform allows authenticated users to access, modify, or delete data belonging to other organizations. This could lead to data corruption or loss by bypassing security checks in the database endpoints.

Users can alter or delete data across organizations.
Confirms cross-tenant data access risks.
Assess ToolJet use and data exposure.

Attack Path

How an attacker could exploit the issue

An attacker with Builder access can exploit this vulnerability by first discovering a victim organization's ID from public application endpoints. They can then use this ID to access specific database endpoints, allowing them to manipulate or delete tables within that organization's data, even without explicit authorization.

Requires authenticated Builder user access.
Triggered by manipulating organization ID in database endpoints.
Risk of data corruption or destruction across tenants.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, authenticated users could manipulate database tables across different organizations within ToolJet. This may affect table schemas, lead to data corruption, or result in permanent data destruction.

Data or system asset at risk: Tenant organization data and schemas.
How exposure could happen: Exploiting path parameter flaws in database endpoints.
Realistic consequence: Permanent data loss or corruption.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in ToolJet affects its database management endpoints, allowing authenticated users to access or modify data across different organizations. This indicates a potential issue for platform teams managing the ToolJet deployment and application owners who rely on its data integrity. The first practical step is to identify all ToolJet instances, confirm their reachability and criticality, identify the accountable owners, and then prioritize remediation based on risk.

Platform and application owners should lead remediation.
Verify affected ToolJet instances and their reachability.
Plan maintenance for data integrity and access controls.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is ToolJet?

ToolJet is a low-code platform designed to help developers and teams build internal business applications quickly. It allows users to connect to various data sources and manage databases through a centralized interface. In enterprise environments, it is often used to create custom tools that interact with company data, making it a critical hub for internal workflows and application development.

What does CVE-2026-82874 mean for data security?

This vulnerability is classified as an authorization bypass (CWE-639). It means the software fails to properly check if a user is permitted to interact with a specific organization's data. Because of this flaw, an authenticated user can perform actions like reading, modifying, or deleting database tables that belong to other organizations, effectively breaking the logical walls intended to separate different tenants.

How is this vulnerability triggered by an attacker?

An attacker needs an account with Builder-level access to the platform. The trigger involves identifying a victim's organization ID, which can be found via public application endpoints, and then inserting that ID into the path parameters of specific database management endpoints. Simply being logged in as a standard user without this specific manipulation does not trigger the vulnerability; it requires the intentional targeting of an external organization ID.

Is my instance at risk according to Halo Surface Signal?

Yes, if your instance is internet-facing, it is considered highly relevant. Halo Surface Signal identifies ToolJet as a platform typically exposed to the internet to support remote users. Because the affected database management endpoints are accessible to authenticated platform users, an internet-reachable deployment significantly increases the likelihood that these sensitive operations could be accessed or abused by unauthorized parties.

What steps should I take if I run ToolJet?

First, verify which instances you have and confirm their current version. Since this issue is addressed in versions prior to 3.16.208, you should work with your platform team to prioritize patching to the latest secure version. Additionally, assess who holds Builder access in your environment and ensure that access controls are strictly managed while you plan for the necessary maintenance to restore full data integrity protections.

References

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.