CVE-2026-48153: Budibase: SSRF via OAuth2 token endpoint URL reaches internal hosts and cloud metadata
Budibase is an open-source low-code platform. Prior to 3.39.0, fetchToken in the OAuth2 SDK makes a POST to a builder-supplied URL with plain node-fetch, skipping the blacklist.isBlacklisted check that every other outbound fetch path in the codebase uses. The Joi schema for the OAuth2 URL has no scheme or host restriction. This vulnerability is fixed in 3.39.0.
HarborGuard Analysis
HarborGuard analysisSynopsis
This is a server-side request forgery (SSRF) vulnerability in Budibase, an open-source low-code platform. A network-accessible attacker with a low-privilege account can supply a crafted URL as the OAuth2 token endpoint, causing the Budibase server to make an outbound HTTP POST to any internal host, including cloud metadata services such as AWS IMDSv1 (169.254.169.254). Successful exploitation reads sensitive internal data and allows limited tampering with internal services. HarborGuard is tracking this advisory and will make a patched-image rebuild available the moment an upstream fix is published.
HarborGuard Coverage
Detection is available across every HarborGuard environment: the CVE is ingested from upstream advisory feeds within minutes of publication and matched against all customer images, including custom-built images that bundle Budibase or its SDK components. Any image found running a Budibase version below 3.39.0 is flagged immediately.
AvailableHarborGuard scores this finding at CVSS 8.5 HIGH and weights it against each environment's compliance policy before routing the alert to the appropriate team inbox. Per-environment policy rules can escalate or suppress the finding based on factors such as internet exposure, data classification, or regulatory scope.
AvailableBecause no upstream fix version has been published yet, HarborGuard re-checks the advisory on every ingest cycle and will make a patched-image rebuild available automatically the moment the upstream project ships a fix. Customers with auto-remediation enabled will receive the rebuild, a regression-test run, and a pull request opened against affected workloads without manual intervention.
Pending upstreamExploit Conditions
- Network reachabilityRequired
The attacker must reach the Budibase API over the network; the vulnerability is exposed on any internet- or intranet-facing Budibase deployment.
- AuthenticationRequired
Any low-privilege Budibase account is sufficient; no administrative rights are needed to supply a crafted OAuth2 token endpoint URL.
- Victim interactionNot required
No victim action is needed; the attacker submits the malicious URL directly through the API and the server-side fetch executes automatically.
- Attack complexityDetail
The exploit is reliable and condition-free; no race conditions or specific memory layout is required to trigger the unguarded outbound fetch.
Blast Radius
- Reads responses from internal HTTP services, including cloud instance metadata endpoints (e.g. AWS IMDSv1), potentially exposing IAM credentials, instance identity documents, and environment secrets.
- Reads any plaintext data served by internal hosts that accept unauthenticated HTTP POST requests, such as monitoring endpoints, internal APIs, or container sidecar services.
- Sends attacker-controlled POST body content to internal services, allowing limited manipulation of services that act on inbound POST data without authentication.
How HarborGuard Handles This
Available on HarborGuard: because no upstream fix has been published for this vulnerability, HarborGuard monitors the advisory on every ingest cycle and will automatically make a patched-image rebuild available the moment Budibase ships version 3.39.0 or later. For customers with auto-remediation enabled, the rebuild will trigger a regression-test run and open a pull request against affected workloads without manual steps. While no patch is available, compensating controls worth considering include applying egress network policies to Budibase pod or container egress to block access to link-local ranges (169.254.0.0/16) and other non-routable internal CIDRs, enabling IMDSv2 (token-required mode) on cloud instances to limit metadata exposure if the SSRF fires, and restricting the Budibase builder role to trusted internal users so the low-privilege authentication barrier carries more practical weight. HarborGuard will surface the rebuild as soon as upstream publishes.
Metrics
- CVSS v3.1
- 8.5
- Severity
- HIGH
- Fixed in
- —
- Affected Products
- 1
- Budibase / budibase< 3.39.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N