dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-55412

HIGH · 8.3 CVSS v3.1 Published 2026-06-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
92/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In ToolJet prior to 3.20.178-lts, the RestAPI data source component validates hostname strings for private IP addresses but fails to validate the resolved IP after DNS resolution. Attackers can bypass this filter using DNS names like 169.254.169.254.nip.io that resolve to Azure's IMDS link-local address (169.254.169.254), enabling authenticated users to exfiltrate Azure managed identity tokens from AKS production clusters.

MitigationUpgrade to ToolJet version 3.20.178-lts or later, which implements proper IP address validation after DNS resolution. Until patched, disable the RestAPI data source for untrusted users or restrict network egress from the ToolJet server.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check ToolJet version
    Examine the installed ToolJet version (e.g., from package.json, docker image tag, or admin panel about page) and compare it to the affected range: any version prior to 3.20.178-lts
    Affected if Installed version is before 3.20.178-lts
  2. Verify RestAPI data source is enabled
    Log into ToolJet as an administrator and navigate to the data sources configuration or check the database table where data sources are stored. Confirm whether the RestAPI connector is enabled and available for users.
    Affected if RestAPI data source is enabled and accessible to users
  3. Identify users with RestAPI access
    Review user permissions and roles in ToolJet to determine which users or groups can create or edit RestAPI data source queries. Check for any untrusted or low-privilege users with this capability.
    Affected if Untrusted or low-privilege users can configure RestAPI data sources
  4. Confirm network egress to Azure IMDS
    Check if the ToolJet server has outbound network access to Azure link-local addresses (169.254.169.254) or can resolve DNS names that point to these addresses (such as *.nip.io domains)
    Affected if ToolJet server can reach Azure IMDS IP 169.254.169.254 or resolve DNS names targeting it

You are affected if running ToolJet version before 3.20.178-lts with RestAPI data source enabled for users who can reach Azure link-local network from the ToolJet server.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to ToolJet version 3.20.178-lts or later, which implements proper IP address validation after DNS resolution. Until patched, disable the RestAPI data source for untrusted users or restrict network egress from the ToolJet server.

Recommended fix High confidence

3.20.178-lts

  1. Verify current ToolJet deployment version using `docker ps` or your deployment manifest
  2. Backup current database and configuration files
  3. Update ToolJet deployment to version 3.20.178-lts
  4. For Docker: update image tag to `tooljet/tooljet:3.20.178-lts` and recreate containers
  5. For Kubernetes: update the image in your deployment manifest and apply changes
  6. Verify the upgrade was successful by checking the application version
  7. Test that the RestAPI data source component now properly validates resolved IP addresses, not just hostname strings
  8. Confirm that DNS names like 169.254.169.254.nip.io are now blocked when they resolve to private/link-local addresses

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-55412 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-55412 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data