Quick answers
- Is CVE-2026-55413 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-55413 being exploited in the wild.
- How severe is CVE-2026-55413?
- Informational severity, with a CVSS score of 9.9, published 25 June 2026.
- Which products and versions are affected?
- ToolJet < 3.20.178-lts.
- Is there a fix for CVE-2026-55413?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-55413 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-55413?
- 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
A vulnerability in ToolJet's plugin management allows an authenticated user with the 'builder' role to overwrite globally-shared marketplace plugins. The root cause is a lack of authorization boundaries on the 'PATCH /api/plugins/:id' endpoint, which fails to restrict plugin modifications to specific organizations or administrative users. An attacker can point a plugin's repository field to a malicious GitHub repository containing a crafted 'index.js' payload. When any user on the instance triggers a query using the poisoned plugin, the malicious code executes server-side via Node.js 'vm.runInNewContext()'. Because the sandbox is configured with full access to 'require' and 'process', the attacker achieves full Remote Code Execution (RCE). This issue is fixed in version 3.20.178-lts.
Affected products
- ToolJet ToolJet < 3.20.178-lts
Timeline
- 2026-06-12: advisory: GitHub Security Advisory published
- 2026-06-25: disclosed: CVE published to NVD