dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-55413

CRITICAL · 9.4 CVSS v4.0 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 →
100/100
Remediation priority · Urgent
Remotely reachable 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, 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.

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

Authenticated users with builder role (even free tier) can overwrite globally-shared marketplace plugins with arbitrary JavaScript containing Node.js primitives (require, process). When other users execute queries using those compromised plugins, the malicious code runs server-side with full RCE capabilities, effectively poisoning the entire ToolJet instance's plugin ecosystem.

MitigationImmediately upgrade to version 3.20.178-lts or later. Audit all marketplace plugins for unauthorized modifications and review builder-role user activity logs to identify potential exploitation.

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
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Identify installed ToolJet version
    Check the version file or running instance metadata (commonly found in package.json, version endpoint, or admin panel)
    Affected if Version is earlier than 3.20.178-lts (the patched release)
  2. Enumerate builder role users
    Query the users table or admin interface for accounts with builder role, noting tier status (free tier users included)
    Affected if Any builder role users exist, especially on free tier, providing potential attack vector
  3. Inspect marketplace plugin files
    Examine globally-shared plugin source files in the plugins directory for unauthorized JavaScript modifications, particularly looking for Node.js primitives (require, process, exec, child_process)
    Affected if Any marketplace plugin contains unexpected Node.js primitives or suspicious code injection
  4. Review builder role activity logs
    Audit authentication and plugin modification logs for builder role users, focusing on marketplace plugin write operations
    Affected if Logs show plugin write/modification actions from builder role users that were not initiated by administrators
  5. Check plugin execution flow
    Verify that marketplace plugins execute server-side with access to Node.js runtime by testing plugin query execution
    Affected if Plugins execute server-side code allowing Node.js primitives to run (this is the vulnerable behavior)

User is affected if running ToolJet version earlier than 3.20.178-lts AND has builder role users with access to modify marketplace plugins, or if marketplace plugins already contain injected Node.js primitives.

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

Immediately upgrade to version 3.20.178-lts or later. Audit all marketplace plugins for unauthorized modifications and review builder-role user activity logs to identify potential exploitation.

Recommended fix High confidence

3.20.178-lts

  1. Upgrade ToolJet to version 3.20.178-lts or later to remediate this vulnerability
  2. Verify the upgrade by checking the ToolJet version after completion
  3. Test that marketplace plugins function correctly after the upgrade
  4. Ensure that only trusted users have builder role permissions to manage plugins

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
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-55413 — 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-55413 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