Quick answers
- Is CVE-2026-73406 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-73406 being exploited in the wild.
- How severe is CVE-2026-73406?
- Low severity, with a CVSS score of 3.1, published 24 July 2026.
- Which products and versions are affected?
- @budibase/server (npm) SEMVER:introduced=0,last_affected=3.38.1.
- Is there a fix for CVE-2026-73406?
- A patch was published on 2026-07-24: Version 3.40.0 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-73406 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-73406?
- Check whether you run @budibase/server (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an information disclosure flaw in the GET /api/global/users/tenant/:id endpoint, which is registered in the PUBLIC_ENDPOINTS list despite containing a TODO comment stating it "should be an internal api." The endpoint bypasses all authentication and authorization middleware when matched, and the tenantUserLookup controller handler returns the complete PlatformUser object without any field filtering or sanitization, exposing tenantId, userId, email, and ssoId fields. The endpoint accepts either an email address or user ID as input and enables user enumeration through differential response codes (HTTP 200 for existing users vs. HTTP 400 for non-existent users). No authentication is required; the vulnerability is remotely exploitable over the network via simple HTTP requests.
Affected products
- Budibase Budibase <3.40.0
Identifiers
- CVE-2026-73406
- GHSA-hr66-5mqr-8mpx
Timeline
- 2026-07-22: disclosed
- 2026-07-24: patched: Version 3.40.0 released