CVE-2026-25044
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 · uneditedBudibase is an open-source low-code platform. Prior to version 3.33.4, the bash automation step executes user-provided commands using execSync without proper sanitization or validation. User input is processed through processStringSync which allows template interpolation, potentially allowing arbitrary command execution. This issue has been patched in version 3.33.4.
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 confidenceThe bash automation step in Budibase versions prior to 3.33.4 executes user-provided commands through Node.js execSync without sanitization. The processStringSync function allows template interpolation, enabling attackers to inject arbitrary shell commands. This is a command injection vulnerability in the low-code platform's automation feature.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 3.33.4CVSS 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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Budibase installation versionAccess the Budibase admin panel or check the package.json/version file in the Budibase installation directory. Run: grep -r '"version"' /path/to/budibase/package.json or check the About section in the admin UI.Affected if The installed version is below 3.33.4 (e.g., 3.33.3, 3.32.x, or earlier)
-
Locate automation workflows using bash stepsNavigate to the Automation section in the Budibase admin panel. Review all automation workflows and identify any that contain a "Bash" or "Execute Script" step type.Affected if Any automation workflow contains a bash/execute script step and the Budibase version is below 3.33.4
-
Inspect bash automation step configurationsOpen each bash automation step in the workflow builder. Examine the script content and identify any fields that accept user input (query parameters, form inputs, row triggers).Affected if A bash step references user-provided variables or inputs in its script without validation (e.g., {{ context.params.input }})
-
Review automation trigger sourcesCheck the trigger configuration for each bash automation to determine what data sources feed into the bash step (HTTP requests, form submissions, row create/update triggers).Affected if The bash step processes input from untrusted sources such as public webhooks, user-submitted forms, or external HTTP endpoints
-
Audit automation execution logsAccess the automation run history in Budibase. Review recent executions of bash steps and inspect input values passed during execution.Affected if Input values contain shell metacharacters (|, ;, &&, $, `, >, <) or unexpected command-like strings that were executed
You are affected if Budibase version is below 3.33.4 AND any automation workflow contains a bash step that processes user-supplied input without validation.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.33.4
Upgrade to Budibase version 3.33.4 or later. Until patched, restrict or disable the bash automation step for untrusted users.
3.33.4
- Identify all Budibase installations running versions prior to 3.33.4
- Plan and schedule a maintenance window for the upgrade
- Back up your Budibase data and configuration before upgrading
- Upgrade Budibase to version 3.33.4 or later
- After upgrading, verify that bash automation steps function correctly with the security fix in place
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
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 locallyCheck whether your project pulls in CVE-2026-25044 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-25044 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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