Vulnerability in ToolJet (CVE-2026-55411)
Summary
Vulnerability in ToolJet (CVE-2026-55411). Confidential information can be exposed externally. Exploitable via POST /api/data-sources/decrypt. Mitigation: upgrade to 3.20.1780-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.1780-lts, the authenticated endpoint POST /api/data-sources/decrypt returns the decrypted plaintext for any credential whose credential_id is supplied in the request body. Unlike every neighbouring data-source route, this handler is not protected by ValidateDataSourceGuard, does not receive the calling @User(), and the underlying CredentialsService.getValue() looks the credential up by id only, with no organization scoping. As a result, any authenticated user of any organization can decrypt the data-source secrets of any other organization by supplying that organization's credential_id — a cross-tenant confidentiality breach. This vulnerability is fixed in 3.20.1780-lts.
Source: NIST National Vulnerability Database NVD
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-55411 has been found in ToolJet.
Attackers can target a specific entry point like POST /api/data-sources/decrypt over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.8/10.
What to do: upgrade ToolJet to 3.20.1780-lts or later.
If unsure, ask your IT team or search "ToolJet CVE-2026-55411" on the vendor's site.
CVE-2026-55411 (ToolJet) — CWE-639 / CVSS v3 6.8
Attack vector: adjacent-network / no user interaction
Attack surface: POST /api/data-sources/decrypt
Patched: 3.20.1780-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.
A vulnerability (CWE-639) exists in ToolJet. Attackers reach the vulnerable code path via POST /api/data-sources/decrypt.
Check the vendor advisory for the affected versions of ToolJet. Attack surface: POST /api/data-sources/decrypt.
Severity: Medium (CVSS 6.8/10). Confidential information can be exposed externally.
Update to 3.20.1780-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 POST /api/data-sources/decrypt requests with malformed payloads or SQL meta-characters. 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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /api/data-sources/decrypt' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/data-sources/decryptへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade ToolJet to 3.20.1780-ltsステージング環境で 3.20.1780-lts に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /api/data-sources/decrypt on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- web github.com