Quick answers
- Is CVE-2026-82874 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82874 being exploited in the wild.
- How severe is CVE-2026-82874?
- Critical severity, with a CVSS score of 9.9, published 31 August 2026.
- Which products and versions are affected?
- ToolJet before v3.16.208.
- Is there a fix for CVE-2026-82874?
- A patch was published on 2026-08-07: Fix released in v3.16.208 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-82874 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-82874?
- Check whether you run ToolJet at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a cross-tenant authorization bypass (CWE-639) in the tooljet-db controller (/server/src/modules/tooljet-db/controller.ts). The root cause is that all schema operation endpoints (create table, drop table, add/drop columns, etc.) accept an organizationId path parameter that is passed directly to backend operations without validating that the authenticated user belongs to that organization. The ability factory only checks the user's role against the tj-workspace-id HTTP header (user's own workspace) and never cross-validates it against the path parameter. Any authenticated Builder user can craft requests with arbitrary organizationId values to perform read and write operations on other tenants' databases. Victim organization IDs are discoverable pre-authentication via GET /api/apps/slugs/:slug on public apps, which leak the owning organization's UUID. The fix is available in v3.16.208, which adds proper tenant validation similar to the organization-validate guard already used in data-sources controllers.
Affected products
- ToolJet ToolJet before v3.16.208
Timeline
- 2026-08-31: disclosed
- 2026-08-07: patched: Fix released in v3.16.208