dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-48146

HIGH · 7.7 CVSS v3.1 Published 2026-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
Budibase is an open-source low-code platform. Prior to 3.39.0, the OAuth2 token fetch function in packages/server/src/sdk/workspace/oauth2/utils.ts uses raw fetch(config.url) with no SSRF protection. The safe wrapper fetchWithBlacklist() exists in the same codebase and is used in every other outbound HTTP call (automation steps, plugin downloads, object store), but was not applied to the OAuth2 token endpoint. A user with BUILDER role can point the OAuth2 token URL to internal services (CouchDB, cloud metadata) to exfiltrate sensitive data. This vulnerability is fixed in 3.39.0.

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 confidence

Budibase versions prior to 3.39.0 contain a Server-Side Request Forgery (SSRF) vulnerability in the OAuth2 token fetch function. The code uses raw fetch(config.url) without SSRF protection, allowing a user with BUILDER role to specify internal service URLs (e.g., CouchDB, cloud metadata endpoints) as the OAuth2 token endpoint and exfiltrate sensitive data from those internal services.

MitigationUpgrade Budibase to version 3.39.0 or later, which applies the existing fetchWithBlacklist() safe wrapper to the OAuth2 token fetch function.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Changed
Confidentiality
High
Integrity
None
Availability
None

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Budibase version
    Locate the Budibase installation and check its version number. This is typically visible in the UI footer, or in package.json / version files within the Budibase deployment directory.
    Affected if Installed version is prior to 3.39.0 (e.g., 3.38.x, 3.37.x, etc.)
  2. Verify OAuth2 configuration exists
    Check if any OAuth2 provider configurations are present in the Budibase settings or configuration files. Look for configured OAuth2 token endpoints in the platform settings or environment config.
    Affected if OAuth2 providers are configured and a token endpoint URL is stored in the configuration.
  3. Confirm BUILDER role access
    Review user accounts and their assigned roles within Budibase. Identify users holding the BUILDER role, which grants elevated platform configuration privileges.
    Affected if At least one user account has the BUILDER role assigned.

The environment is affected if Budibase version is below 3.39.0, OAuth2 providers are configured, and a user with BUILDER role exists who could exploit the unprotected fetch(config.url) call in the OAuth2 token fetch function.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Budibase to version 3.39.0 or later, which applies the existing fetchWithBlacklist() safe wrapper to the OAuth2 token fetch function.

Recommended fix High confidence

3.39.0

  1. 1. Back up your current Budibase installation and database
  2. 2. Stop the Budibase server
  3. 3. Update Budibase to version 3.39.0 or later using your package manager or deployment method (e.g., Docker image tag, npm update, or Helm chart version)
  4. 4. Verify the installation by checking that the packages/server/src/sdk/workspace/oauth2/utils.ts file now uses fetchWithBlacklist() instead of raw fetch()
  5. 5. Restart the Budibase server
  6. 6. Test OAuth2 functionality to confirm the fix is working

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-48146 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-48146 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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