Quick answers
- Is CVE-2026-25044 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-25044 being exploited in the wild.
- How severe is CVE-2026-25044?
- High severity, with a CVSS score of 8.8, published 3 April 2026.
- Which products and versions are affected?
- @budibase/server (npm) SEMVER:introduced=0,fixed=3.33.4.
- Is there a fix for CVE-2026-25044?
- Yes. @budibase/server (npm): upgrade to 3.33.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-25044 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-25044?
- Check whether you run @budibase/server (npm) 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.
How to fix
- @budibase/server (npm): upgrade to 3.33.4 or later
npm install @budibase/server@3.33.4
Technical details
An OS command injection vulnerability exists in Budibase's bash automation step within 'packages/server/src/automations/steps/bash.ts'. The application uses 'execSync' to run user-provided code after processing it through 'processStringSync', which supports template interpolation. Because the input is not properly sanitized or validated, an attacker with 'low' privileges (sufficient to create or modify automations) can inject malicious shell commands using standard syntax like $(command) or command chaining. This results in remote code execution (RCE) on the host system. The vulnerability is addressed in version 3.33.4 by implementing command validation and switching to safer execution methods.
Affected products
- Budibase Budibase < 3.33.4
Identifiers
- CVE-2026-25044
- GHSA-gjw9-34gf-rp6m
Timeline
- 2026-04-02: advisory: GitHub Security Advisory published
- 2026-04-03: disclosed: CVE published to NVD
- 2026-04-03: patched: Fix released in version 3.33.4