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-100688 Overview
CVE-2026-100688 is a cross-tenant information disclosure vulnerability in Budibase server versions before 3.45.0. The flaw resides in the GET /api/applications/:appId/appPackage endpoint, which fails to enforce tenant boundaries when returning application data. Authenticated users can supply any victim tenant's application identifier and retrieve the associated application metadata and source code. Exposed data includes navigation structure, role names, internal screen URLs, embedded JavaScript snippets, and user identifiers. The vulnerability is classified under CWE-639: Authorization Bypass Through User-Controlled Key.
Critical Impact
Any authenticated Budibase user can read another tenant's full application package, including source code and user identifiers, by iterating app IDs against a single API endpoint.
Affected Products
- Budibase server versions prior to 3.45.0
- Multi-tenant Budibase deployments (self-hosted and cloud)
- Applications relying on Budibase tenant isolation for intellectual property protection
Discovery Timeline
- 2026-09-26 - CVE-2026-100688 published to NVD
- 2026-09-28 - Last updated in NVD database
Technical Details for CVE-2026-100688
Vulnerability Analysis
The vulnerability exists in Budibase's application package retrieval endpoint. When a client issues GET /api/applications/:appId/appPackage, the server loads and returns the full application definition. The handler validates that the caller is authenticated but does not verify that the requested appId belongs to the caller's tenant.
Because application IDs are the only authorization key, any authenticated user from any tenant can request packages belonging to other tenants. The returned payload contains the complete design-time representation of the application, including routing, roles, screens, and inline scripts. This exposes both operational data and intellectual property across tenant boundaries.
Root Cause
The root cause is a missing tenant-scope authorization check on a user-controlled identifier. The endpoint trusts the appId path parameter without cross-referencing it against the authenticated user's tenant context. This is a textbook Insecure Direct Object Reference (IDOR) pattern mapped to CWE-639.
Attack Vector
An attacker needs only a valid Budibase account on any tenant. They enumerate or acquire a target tenant's application ID and send an authenticated HTTP GET request to /api/applications/<target_app_id>/appPackage. The server returns the full application package without rejecting the request. No elevated privileges, user interaction, or network adjacency are required beyond standard HTTPS access.
The vulnerability is described in the GitHub Security Advisory GHSA-4946-qf2m-wrh5 and the Vulncheck advisory.
Detection Methods for CVE-2026-100688
Indicators of Compromise
- Repeated authenticated requests to /api/applications/:appId/appPackage with varying appId values from a single user or session
- Access patterns where a user's tenant context does not match the tenant that owns the requested appId
- High-volume GET activity against the appPackage endpoint outside normal development workflows
- Unexpected egress of application JSON responses to non-standard client IPs or user agents
Detection Strategies
- Enable verbose HTTP access logging on the Budibase server and correlate appId path parameters with the authenticated user's tenant identifier
- Alert when a single account requests application packages belonging to multiple tenants within a short time window
- Deploy a web application firewall rule that inspects /api/applications/*/appPackage requests and flags responses larger than a baseline threshold
Monitoring Recommendations
- Centralize Budibase application logs and reverse-proxy logs in a SIEM for cross-tenant query analysis
- Baseline normal application package retrieval patterns per user and generate anomalies for lateral enumeration
- Monitor authentication logs for newly created low-privilege accounts followed by API enumeration activity
How to Mitigate CVE-2026-100688
Immediate Actions Required
- Upgrade Budibase server to version 3.45.0 or later on all self-hosted deployments
- Audit historical access logs for the /api/applications/:appId/appPackage endpoint to identify prior cross-tenant retrieval
- Rotate any secrets, API keys, or credentials that may have been embedded in application JavaScript snippets or metadata
- Review and tighten account provisioning so that unknown or low-trust users cannot obtain authenticated sessions
Patch Information
Budibase addressed the vulnerability in version 3.45.0. Administrators should apply the patch following upgrade guidance in the GitHub Security Advisory GHSA-4946-qf2m-wrh5. Cloud-hosted Budibase tenants on the vendor's managed service receive the fix centrally.
Workarounds
- Restrict network access to the Budibase API to trusted developer networks or VPN segments until patching completes
- Add a reverse-proxy policy that rejects /api/applications/:appId/appPackage requests when the appId does not match an allowlist for the authenticated session
- Disable self-service account registration on multi-tenant Budibase instances to limit the pool of authenticated attackers
# Example NGINX rule to block the vulnerable endpoint until upgrade
location ~ ^/api/applications/[^/]+/appPackage$ {
deny all;
return 403;
}
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

