Quick answers
- Is CVE-2026-54344 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-54344 being exploited in the wild.
- How severe is CVE-2026-54344?
- Medium severity, with a CVSS score of 4.7, published 8 July 2026.
- Which products and versions are affected?
- ToolJet < 3.20.180.
- Is there a fix for CVE-2026-54344?
- A patch was published on 2026-07-08: Fixed in version 3.20.180 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-54344 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-54344?
- 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 command injection vulnerability exists in ToolJet's 'render-preview-deploy.yml' GitHub Actions workflow. The workflow directly interpolates the 'github.event.comment.body' context into a bash script within a 'run' step without sanitization or using environment variables. Because the workflow triggers on any comment containing '/deploy-ee' without verifying the author's permissions, an unauthenticated attacker can craft a comment that breaks out of the bash conditional to execute arbitrary code on the CI runner. This allows for the exfiltration of sensitive secrets, including RENDER_API_KEY, CUSTOM_GITHUB_TOKEN, and SMTP credentials. The issue is fixed in version 3.20.180 by using environment variables for shell expansion and adding author association checks.
Affected products
- ToolJet ToolJet < 3.20.180
Timeline
- 2026-06-30: advisory: GitHub Security Advisory GHSA-4pm2-w6g5-28mm published
- 2026-07-08: disclosed: CVE-2026-54344 published to NVD
- 2026-07-08: patched: Fixed in version 3.20.180