Quick answers
- Is CVE-2026-55412 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-55412 being exploited in the wild.
- How severe is CVE-2026-55412?
- High severity, with a CVSS score of 8.3, published 25 June 2026.
- Which products and versions are affected?
- ToolJet < 3.20.178-lts.
- Is there a fix for CVE-2026-55412?
- A patch was published on 2026-06-25: CVE published and fix confirmed in 3.20.178-lts Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-55412 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-55412?
- 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 Server-Side Request Forgery (SSRF) exists in ToolJet's RestAPI data source component due to improper validation of hostnames. The `ssrf-protection.ts` filter only checks the literal hostname string against a blocklist rather than validating the resolved IP address. An attacker can use DNS rebinding or services like 'nip.io' (e.g., 169.254.169.254.nip.io) to resolve to restricted internal addresses such as the Azure Instance Metadata Service (IMDS). This allows an authenticated user to retrieve sensitive Azure managed identity tokens, potentially compromising the AKS production cluster. The vulnerability is fixed in version 3.20.178-lts by implementing DNS resolution before filter validation.
Affected products
- ToolJet ToolJet < 3.20.178-lts
Timeline
- 2026-05-24: disclosed: Vulnerability discovered and reported to vendor
- 2026-06-12: advisory: GitHub Security Advisory published
- 2026-06-25: patched: CVE published and fix confirmed in 3.20.178-lts