Budibase Unrestricted Server-Side Request Forgery (SSRF) via REST Datasource Query Preview

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.7 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N

EPSS

• CVE-2026-33226: 0.37% estimated exploitation activity in the next 30 days; percentile 31.33 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The REST datasource query preview endpoint (POST /api/queries/preview) makes server-side HTTP requests to any URL supplied by the user in 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. Details The vulnerable handler is in packages/server/src/api/controllers/query.ts (preview()). It reads fields.path from the request body and passes it directly to the REST HTTP client without any IP or hostname validation: No blocklist exists for: - Loopback (127.0.0.1, ::1) - RFC 1918 ranges (10.x.x.x, 172.16-31.x.x, 192.168.x.x) - Link-local / cloud metadata (169.254.x.x) - Internal Kubernetes DNS (.svc.cluster.local) The datasourceId field must…

Published by the source

18 Mar 2026, 20:22 UTC

Last modified by the source

25 Mar 2026, 19:47 UTC

Source last checked

26 Oct 2026, 12:46 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-4647-wpjq-hh7f

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-4647-wpjq-hh7f

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-33226

Advisory: Budibase Unrestricted Server-Side Request Forgery (SSRF) via REST Datasource Query Preview
IDs: CVE-2026-33226, GHSA-4647-wpjq-hh7f
Record: https://patchnext.com/advisories/cve-2026-33226 (revision 2, source checked 26 Oct 2026, 12:46 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm budibase: affected <= 3.30.6

## Suggested inspection (read-only)
- `npm ls budibase --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on budibase.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-4647-wpjq-hh7f (OSV record GHSA-4647-wpjq-hh7f lists affected ranges: npm budibase >=0 <=3.30.6)
- Verified: https://github.com/advisories/GHSA-4647-wpjq-hh7f (GitHub-reviewed advisory GHSA-4647-wpjq-hh7f lists affected ranges: npm budibase >=0 <=3.30.6)

Commands are suggestions: review each one before running it.