CVE-2026-33226
Budibase is a low code platform for creating internal tools, workflows, and admin panels.
Executive Summary
CVE-2026-33226 is a high severity vulnerability affecting appsec, ai-code. It is classified as Server-Side Request Forgery. Ensure your systems and dependencies are patched immediately to mitigate exposure risks.
Precogs AI Insight
"The primary vulnerability vector is rooted in within Budibase, allowing a lack of rigorous type checking mechanisms. By manipulating this weakness, a threat actor can silently exfiltrate sensitive routing topologies and internal schemas. By intercepting insecure data flows from user input directly to rendering sinks, Precogs is designed to identify exploitable weaknesses before attackers do."
What is this vulnerability?
CVE-2026-33226 is categorized as a critical Code Injection / RCE flaw. Based on our vulnerability intelligence, this issue occurs when the application fails to securely handle untrusted data boundaries.
Budibase is a low code platform for creating internal tools, workflows, and admin panels. In versions from 3.30.6 and prior, the REST datasource query prev...
This architectural defect enables adversaries to bypass intended security controls, directly manipulating the application's execution state or data layer. Immediate strategic intervention is required.
Risk Assessment
| Metric | Value |
|---|---|
| CVSS Base Score | 8.7 (HIGH) |
| Vector String | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N |
| Published | March 20, 2026 |
| Last Modified | March 20, 2026 |
| Related CWEs | CWE-918 |
Impact on Systems
✅ Remote Code Execution: Attackers achieve arbitrary command execution within the context of the application server.
✅ Privilege Escalation: Initial code execution can be exploited to pivot and elevate privileges across the network.
✅ Persistent Backdoors: Attackers can bind reverse shells, modify source files, or inject persistent access mechanisms.
How to fix this issue?
Implement the following strategic mitigations immediately to eliminate the attack surface.
1. Remove Dynamic Evaluation Completely eliminate the use of dynamic evaluation functions (eval(), exec(), system()) on untrusted input.
2. Sandboxing If dynamic execution is an absolute business requirement, isolate the execution environment in tightly constrained, non-networked sandboxes (e.g., restricted WebAssembly or isolated containers).
3. Network Segmentation Restrict outbound traffic from the application server (egress filtering) to prevent reverse shell connections.
Vulnerability Signature
// Vulnerable Node.js Execution
const exec = require('child_process').exec;
const user_domain = req.query.domain;
// VULNERABLE: Injecting user input directly into system shell commands
exec('ping -c 4 ' + user_domain, (error, stdout, stderr) =\> \{
res.send(stdout);
\});
// EXPLOIT PAYLOAD: precogs.ai ; cat /etc/passwd
References and Sources
- NVD — CVE-2026-33226
- MITRE — CVE-2026-33226
- CWE-918 — MITRE CWE
- CWE-918 Details
- Application Security Vulnerabilities
- AI Code Security Vulnerabilities
Vulnerability Code Signature
Attack Data Flow
| Stage | Detail |
|---|---|
| Source | User-supplied URL parameter |
| Vector | Server fetches the user-controlled URL |
| Sink | HTTP request library (e.g., fetch, axios) |
| Impact | Access to internal services, metadata endpoints, or port scanning |
Vulnerable Code Pattern
// ❌ VULNERABLE: Server-Side Request Forgery
app.get('/proxy', async (req, res) => {
const targetUrl = req.query.url;
// Taint sink: unvalidated outbound request
const response = await fetch(targetUrl);
res.send(await response.text());
});
Secure Code Pattern
// ✅ SECURE: Allowlist validation
const ALLOWED_DOMAINS = ['api.partner.com'];
app.get('/proxy', async (req, res) => {
const targetUrl = new URL(req.query.url);
if (!ALLOWED_DOMAINS.includes(targetUrl.hostname)) {
return res.status(403).send("Domain not allowed");
}
// Sanitized outbound request
const response = await fetch(targetUrl.href);
res.send(await response.text());
});
How Precogs Detects This
Precogs API Security Engine actively detects SSRF vulnerabilities by tracking unvalidated URL sinks and enforcing strict allowlist policies.\n