Code Injection in ToolJet (CVE-2026-55413)
Summary
Code injection in ToolJet (CVE-2026-55413). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 3.20.178-lts or later.
Original description
The description as published by the source.
ToolJet is the open-source foundation am AI-native platform for building and deploying internal tools, workflows and AI agents. Prior to 3.20.178-lts, any authenticated user with builder role (free tier) can overwrite a globally-shared marketplace plugin with arbitrary JavaScript that executes server-side with full Node.js access (require, process). The malicious code runs whenever any user on the instance triggers a query using that plugin — achieving both RCE and supply-chain compromise of the entire ToolJet deployment. This vulnerability is fixed in 3.20.178-lts.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-55413 has been found in ToolJet.
Risk of unauthorized operations or information disclosure.
What to do: upgrade ToolJet to 3.20.178-lts or later.
If unsure, ask your IT team or search "ToolJet CVE-2026-55413" on the vendor's site.
CVE-2026-55413 (ToolJet) — CWE-94
Patched: 3.20.178-lts — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Arbitrary code execution (CWE-94) exists in ToolJet.
Check the vendor advisory for the affected versions of ToolJet.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 3.20.178-lts.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'ToolJet' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'ToolJet' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
ToolJetを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade ToolJet to 3.20.178-ltsステージング環境で 3.20.178-lts に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov