SSRF (Server-Side Request Forgery) in ToolJet (CVE-2026-55412)
Summary
SSRF in ToolJet (CVE-2026-55412). 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, there's an SSRF in the RestAPI data source component. The RestAPI data source executes HTTP requests server-side, and its private IP filter only checks the hostname string — not the resolved IP. DNS names like 169.254.169.254.nip.io resolve to the Azure IMDS link-local address and bypass the filter entirely. This allows any authenticated user (free tier) to steal Azure managed identity tokens for the AKS production cluster. 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-55412 has been found in ToolJet.
Risk of unauthorized operations or information disclosure. CVSS score: 8.3/10.
What to do: upgrade ToolJet to 3.20.178-lts or later.
If unsure, ask your IT team or search "ToolJet CVE-2026-55412" on the vendor's site.
CVE-2026-55412 (ToolJet) — CWE-918 / CVSS v3 8.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
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.
SSRF (CWE-918) exists in ToolJet.
Check the vendor advisory for the affected versions of ToolJet.
Severity: High (CVSS 8.3/10). 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