Quick answers
- Is CVE-2026-73617 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-73617 being exploited in the wild.
- How severe is CVE-2026-73617?
- High severity, with a CVSS score of 7.1, published 13 August 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-73617?
- 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-73617 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-73617?
- 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 a NoSQL injection in Budibase's MongoDB query processing. Builders use Handlebars templating with bindings (e.g., {"email": "{{ currentUser.email }}"}) to scope queries per-user; the Handlebars enrichment uses noEscaping: true, then passes the result to JSON.parse. An attacker injects MongoDB operators using a duplicate-key technique (e.g., x", "name": {"$ne": "x"}, "$comment": "payload) that JSON.parse resolves to an operator-based filter. Unlike SQL datasources, which parameterize bindings through interpolateSQL(), the MongoDB path has no equivalent parameterization, allowing injected operators to reach collection.find() unchanged. Any BASIC app user with query execution permission can exploit this to dump collections, execute arbitrary MongoDB operations, or access cross-collection data.
Affected products
- Budibase Budibase <3.40.0
Identifiers
- CVE-2026-73617
- GHSA-pmpg-2mxq-6xwr
Timeline
- 2026-07-24: disclosed
- 2026-07-24: patched: Version 3.40.0 released