CVE-2026-48148: Budibase Unvalidated VectorDB Host Parameter Enables Vulnerability

MODERATE
Advisory Identifier: GHSA-cv96-5348-p5p8
CWE-918
Published
Advisory Summary

CVE-2026-48148 is a MODERATE unvalidated vectordb host parameter enables vulnerability (CWE-918: Server-Side Request Forgery (SSRF)) affecting Budibase libraries in the npm ecosystem. The issue involves unvalidated vectordb host parameter enables ssrf. Remediation is available by upgrading affected packages to version 3.35.3.

CVE-2026-48148 at a Glance

CVE Identifier CVE-2026-48148
GHSA Identifier GHSA-cv96-5348-p5p8
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-918: Server-Side Request Forgery (SSRF)
Affected Product Budibase
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-48148

To remediate this vulnerability, upgrade all affected Budibase dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@budibase/server fixed: 3.35.3
npm install @budibase/server@3.35.3
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls @budibase/server

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-48148, inspect your project dependencies using npm:

npm ls @budibase/server

Analyze the terminal output to locate any version of Budibase in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.35.3), your application is affected.

Note: The npm ls @budibase/server command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-918: Server-Side Request Forgery (SSRF), where the web server receives a url or similar request from an upstream component and retrieves the contents of this url, but it does not sufficiently ensure that the request is being sent to the expected destination. In Budibase, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary The VectorDB configuration endpoint in Budibase accepts a host parameter that undergoes no validation against internal IP ranges, reserved hostnames, or URL schemes. Any authenticated user with builder-level access can supply an arbitrary host value such as `169.254.169.254` or localhost, causing the server to initiate outbound TCP connections to internal network addresses or cloud metadata endpoints on their behalf. ### Details The validator responsible for VectorDB creation and updates defines the host field as `Joi.string().required()`, which enforces only that the value is a non-empty string. No allowlist of external hostnames, no blocklist of RFC 1918 or link-local ranges, and no scheme validation are applied before the value is forwarded to the database SDK for connection establishment. When a VectorDB entry is created or updated, the SDK uses the supplied host directly to open a TCP connection. Because the connection attempt originates from the Budibase server process, it traverses internal network boundaries that would otherwise be inaccessible to the attacker. Differences in connection timing and error messages between reachable and unreachable hosts allow an attacker to enumerate internal services and determine whether specific addresses are live. In cloud environments, the AWS EC2 metadata service at `169.254.169.254`, the GCP metadata server at `metadata.google.internal`, and equivalent endpoints for other providers are all reachable this way. Builder access is a realistic precondition in multi-tenant or team deployments, as the builder role is intended to allow application development without granting administrative privileges over the underlying infrastructure. ### PoC ```python import requests import time BASE_URL = "https://TARGET_BUDIBASE_INSTANCE" SESSION = requests.Session() login_resp = SESSION.post(f"{BASE_URL}/api/global/auth/default/login", json={ "username": "builder@example.com", "password": "builderpassword" }) token = login_resp.cookies.get("budibase:auth") or login_resp.json().get("token") SESSION.headers.update({"Cookie": f"budibase:auth={token}"}) targets = [ ("169.254.169.254", 80), ("localhost", 5432), ("10.0.0.1", 22), ] for host, port in targets: start = time.time() resp = SESSION.post(f"{BASE_URL}/api/ai/vectordb", json={ "name": f"probe_{host.replace('.', '_')}_{port}", "provider": "pgvector", "host": host, "port": port, "database": "db" }) elapsed = time.time() - start print(f"host={host} port={port} status={resp.status_code} time={elapsed:.2f}s body={resp.text[:200]}") ``` ### Impact An attacker with builder access can use the Budibase server as a proxy to probe internal network topology, determine which hosts and ports are reachable from the server, and potentially interact with unauthenticated internal services including cloud instance metadata endpoints. In environments where cloud metadata endpoints expose credentials or instance identity documents, successful retrieval of metadata could lead to privilege escalation or lateral movement within the cloud environment. The attack requires no interaction beyond a single authenticated API request per probe target.

CVE-2026-48148 Affected Budibase Versions

1 component(s)
Fixed Versions:
3.35.3
Product / Package Ecosystem Affected Versions Fixed Version
@budibase/server
npm
< 3.35.3
3.35.3

References

Frequently Asked Questions

What is CVE-2026-48148?
CVE-2026-48148 is a security vulnerability in Budibase involving Unvalidated VectorDB Host Parameter Enables SSRF under CWE-918: Server-Side Request Forgery (SSRF).
Which Budibase versions are affected?
Affected versions include releases prior to 3.35.3 across affected packages: @budibase/server.
What version fixes CVE-2026-48148?
Upgrading to 3.35.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @budibase/server affected?
Yes, @budibase/server is affected in releases prior to 3.35.3. Upgrade your dependency to 3.35.3 or later.
What CWE is associated with CVE-2026-48148?
CVE-2026-48148 is classified under CWE-918: Server-Side Request Forgery (SSRF) (The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.).
How can I check npm dependencies for CVE-2026-48148?
Run the dependency tree command: 'npm ls @budibase/server'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-cv96-5348-p5p8",
  "modified" : "2026-06-12T18:27:45Z",
  "published" : "2026-06-12T18:27:45Z",
  "aliases" : [ "CVE-2026-48148" ],
  "summary" : "Budibase: Unvalidated VectorDB Host Parameter Enables SSRF",
  "details" : "### Summary\n\nThe VectorDB configuration endpoint in Budibase accepts a host parameter that undergoes no validation against internal IP ranges, reserved hostnames, or URL schemes. Any authenticated user with builder-level access can supply an arbitrary host value such as `169.254.169.254` or localhost, causing the server to initiate outbound TCP connections to internal network addresses or cloud metadata endpoints on their behalf.\n\n### Details\n\nThe validator responsible for VectorDB creation and updates defines the host field as `Joi.string().required()`, which enforces only that the value is a non-empty string. No allowlist of external hostnames, no blocklist of RFC 1918 or link-local ranges, and no scheme validation are applied before the value is forwarded to the database SDK for connection establishment.\n\nWhen a VectorDB entry is created or updated, the SDK uses the supplied host directly to open a TCP connection. Because the connection attempt originates from the Budibase server process, it traverses internal network boundaries that would otherwise be inaccessible to the attacker. Differences in connection timing and error messages between reachable and unreachable hosts allow an attacker to enumerate internal services and determine whether specific addresses are live. In cloud environments, the AWS EC2 metadata service at `169.254.169.254`, the GCP metadata server at `metadata.google.internal`, and equivalent endpoints for other providers are all reachable this way.\n\nBuilder access is a realistic precondition in multi-tenant or team deployments, as the builder role is intended to allow application development without granting administrative privileges over the underlying infrastructure.\n\n### PoC\n\n```python\nimport requests\nimport time\n\nBASE_URL = \"https://TARGET_BUDIBASE_INSTANCE\"\nSESSION = requests.Session()\n\nlogin_resp = SESSION.post(f\"{BASE_URL}/api/global/auth/default/login\", json={\n    \"username\": \"builder@example.com\",\n    \"password\": \"builderpassword\"\n})\ntoken = login_resp.cookies.get(\"budibase:auth\") or login_resp.json().get(\"token\")\nSESSION.headers.update({\"Cookie\": f\"budibase:auth={token}\"})\n\ntargets = [\n    (\"169.254.169.254\", 80),\n    (\"localhost\", 5432),\n    (\"10.0.0.1\", 22),\n]\n\nfor host, port in targets:\n    start = time.time()\n    resp = SESSION.post(f\"{BASE_URL}/api/ai/vectordb\", json={\n        \"name\": f\"probe_{host.replace('.', '_')}_{port}\",\n        \"provider\": \"pgvector\",\n        \"host\": host,\n        \"port\": port,\n        \"database\": \"db\"\n    })\n    elapsed = time.time() - start\n    print(f\"host={host} port={port} status={resp.status_code} time={elapsed:.2f}s body={resp.text[:200]}\")\n```\n\n### Impact\n\nAn attacker with builder access can use the Budibase server as a proxy to probe internal network topology, determine which hosts and ports are reachable from the server, and potentially interact with unauthenticated internal services including cloud instance metadata endpoints. In environments where cloud metadata endpoints expose credentials or instance identity documents, successful retrieval of metadata could lead to privilege escalation or lateral movement within the cloud environment. The attack requires no interaction beyond a single authenticated API request per probe target.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@budibase/server"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.35.3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/Budibase/budibase/security/advisories/GHSA-cv96-5348-p5p8"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-48148"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/Budibase/budibase"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-918" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-12T18:27:45Z",
    "nvd_published_at" : "2026-05-27T18:16:27Z"
  }
}