Raw vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:NSummary
CVE-2026-33226 is a high-severity SSRF (CWE-918) vulnerability in Budibase Budibase. Its CVSS base score is 8.7 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 30th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-4 (Information Flow Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-33226 is a server-side request forgery vulnerability (CWE-918) affecting Budibase, a low-code platform for building internal tools, workflows, and admin panels. In versions 3.30.6 and prior, the REST datasource query preview endpoint (POST /api/queries/preview) executes server-side HTTP requests to arbitrary URLs provided by users in the fields.path parameter without any validation. This flaw has a CVSS v3.1 base score of 8.7 (AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N), indicating high confidentiality and integrity impacts with changed scope.
An authenticated administrator can exploit this vulnerability remotely over the network with low complexity. By supplying malicious URLs, the attacker tricks the Budibase server into making requests to internal services not exposed to the internet, such as cloud metadata endpoints on AWS, GCP, or Azure, internal databases, Kubernetes APIs, and other pods on the internal network. On GCP deployments, this enables theft of OAuth2 tokens with cloud-platform scope, granting full access to GCP resources. Across any deployment, it allows comprehensive internal network enumeration.
The primary advisory, published via GitHub Security Advisory GHSA-4647-wpjq-hh7f, confirms the issue and notes that no publicly available patches exist as of the CVE publication date on 2026-03-20. Security practitioners should restrict admin access, monitor query preview endpoint usage, and consider network segmentation or proxying internal requests until a patch is released.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-13879
Vulnerability Data
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 preview endpoint (POST /api/queries/preview) makes server-side HTTP requests to any URL supplied by the user in…
more
fields.path with no validation. An authenticated admin can reach internal services that are not exposed to the internet — including cloud metadata endpoints (AWS/GCP/Azure), internal databases, Kubernetes APIs, and other pods on the internal network. On GCP this leads to OAuth2 token theft with cloud-platform scope (full GCP access). On any deployment it enables full internal network enumeration. At time of publication, there are no publicly available patches.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.3.6V1.5.3V5.3.2V10.4.7
Mitigating Controls (NIST 800-53 r5) AI
Information flow enforcement can restrict which destinations the server is allowed to contact on behalf of users.
Input validation directly stops untrusted URLs from being accepted and fetched without destination checks.
Boundary protection limits the network reach of server-initiated requests even if SSRF occurs.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure development practices directly include input validation and destination allow-listing that prevent SSRF.
Runtime monitoring of web applications and services can detect anomalous outbound requests indicative of SSRF.
Vulnerability identification processes can discover and record SSRF flaws in web applications.
Network segmentation and egress controls can limit the damage from successful SSRF requests.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Operational threat data describing SSRF campaigns can be used to tighten outbound-request allow-lists and detection rules before attackers exploit them.