Skip to main content
Vulnerability Database/CVE-2026-100680

CVE-2026-100680: Budibase Information Disclosure Vulnerability

CVE-2026-100680 is an information disclosure vulnerability in Budibase that enables authenticated builders to read arbitrary local files through malicious OpenAPI specifications. This article covers technical details, affected versions, impact assessment, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-100680 Overview

Budibase versions before 3.45.0 contain an arbitrary local file read vulnerability in the OpenAPI/Swagger import validator. The application fails to disable external JSON reference resolution when processing imported specifications. Authenticated users with builder access can embed file:// references in OpenAPI documents submitted to the import endpoint. The server resolves these references and returns file contents, enabling exfiltration of sensitive local files. Attackers can read environment variables containing JWT secrets, API keys, and database credentials. The flaw is categorized as information exposure under [CWE-200].

Critical Impact

Authenticated builders can read arbitrary files on the Budibase server, exposing secrets that enable broader compromise of the application and connected datasources.

Affected Products

  • Budibase versions prior to 3.45.0
  • Budibase OpenAPI/Swagger import functionality
  • Self-hosted and cloud Budibase deployments exposing the builder role

Discovery Timeline

  • 2026-09-26 - CVE-2026-100680 published to NVD
  • 2026-09-28 - Last updated in NVD database

Technical Details for CVE-2026-100680

Vulnerability Analysis

Budibase accepts OpenAPI and Swagger specifications through its import endpoint to generate REST datasource definitions. The import validator parses submitted JSON or YAML documents and resolves $ref pointers to assemble the complete schema. The resolver is not restricted to internal document references or trusted HTTP sources. External references using the file:// scheme are followed by the server-side parser. The resolver reads the referenced path from the local filesystem and inlines its contents into the parsed specification. The expanded specification is then returned to the authenticated builder through the API response, exposing file contents directly to the attacker.

Root Cause

The root cause is missing configuration on the OpenAPI reference resolver. The parser library used by Budibase supports external reference resolution by default and must be explicitly restricted. Versions before 3.45.0 do not disable the file:// protocol handler or restrict base paths. Any $ref value the attacker supplies is treated as a legitimate pointer.

Attack Vector

An authenticated attacker with the builder role crafts an OpenAPI document that includes a $ref such as file:///etc/passwd or file:///app/.env. The attacker submits the document to the OpenAPI import endpoint. The server resolves the reference, embeds the file content into the schema, and returns it in the API response. The attacker reads the response to retrieve the file contents. Repeated requests targeting different paths allow full enumeration of accessible files, including configuration files holding JWT signing secrets and datasource credentials.

No verified public exploit code is available. See the GitHub Security Advisory GHSA-8xr5-pggf-26jq and the VulnCheck Advisory: Budibase Local File Read for additional technical detail.

Detection Methods for CVE-2026-100680

Indicators of Compromise

  • OpenAPI or Swagger import requests containing the string file:// in the request body
  • Unexpected datasource import activity from builder accounts outside normal change windows
  • API responses from the import endpoint containing filesystem content such as /etc/passwd entries or environment variable key names
  • Access or reuse of JWT secrets, API keys, or database credentials shortly after an import event

Detection Strategies

  • Inspect application and reverse proxy logs for POST requests to the Budibase OpenAPI import endpoint and search payloads for file://, $ref, and absolute path patterns
  • Correlate builder-role authentication events with import endpoint usage to identify abnormal account behavior
  • Alert on outbound reuse of credentials sourced from Budibase environment files or configuration directories

Monitoring Recommendations

  • Enable verbose audit logging for datasource creation and OpenAPI import actions
  • Forward Budibase application logs to a centralized SIEM for retention and correlation
  • Monitor filesystem access patterns on the Budibase host for reads of .env, credential, and key material files by the application process

How to Mitigate CVE-2026-100680

Immediate Actions Required

  • Upgrade Budibase to version 3.45.0 or later on all self-hosted deployments
  • Rotate all secrets accessible to the Budibase process, including JWT signing keys, API tokens, and datasource credentials
  • Review builder role assignments and remove unnecessary builder access
  • Audit historical import endpoint traffic for payloads containing file:// references

Patch Information

The maintainers released a fix in Budibase 3.45.0 that disables external JSON reference resolution in the OpenAPI import validator. Refer to the GitHub Security Advisory GHSA-8xr5-pggf-26jq for release notes and upgrade guidance.

Workarounds

  • Restrict the builder role to a minimal set of trusted administrators until the patch is applied
  • Place the Budibase application behind a web application firewall rule that blocks request bodies containing file:// references on import endpoints
  • Run the Budibase process under a dedicated unprivileged account with filesystem access limited to required application directories
  • Store secrets outside the Budibase process environment where feasible, using an external secrets manager
bash
# Example WAF rule concept (ModSecurity) blocking file:// in OpenAPI import bodies
SecRule REQUEST_URI "@contains /api/integrations/rest/openapi" \
    "phase:2,id:1009100680,deny,status:403,log,msg:'Blocked file:// in OpenAPI import',\
    chain"
    SecRule REQUEST_BODY "@rx (?i)file://" "t:none"

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.