Quick answers
- Is CVE-2026-100680 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-100680 being exploited in the wild.
- How severe is CVE-2026-100680?
- High severity, with a CVSS score of 8.1, published 26 September 2026.
- Which products and versions are affected?
- Budibase before 3.45.0.
- Is there a fix for CVE-2026-100680?
- A patch was published on 2026-09-10: Version 3.45.0 includes the fix Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-100680 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-100680?
- Check whether you run Budibase 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 exists in the OpenAPI import validator (POST /api/queries/import/info) where SwaggerParser.validate() is called without the resolve.external:false option, causing @apidevtools/swagger-parser to default to external=true and enable filesystem resolution. An authenticated builder can embed {"$ref":"file:///etc/passwd"} or similar file:// pointers in the OpenAPI spec to trigger arbitrary local file reads; file contents are returned in the import response or inlined during schema validation. The fix is a one-line change to pass the same resolve options to the validate function as the parse and dereference fallback functions already do.
Affected products
- Budibase Budibase before 3.45.0
Timeline
- 2026-09-26: disclosed
- 2026-09-10: patched: Version 3.45.0 includes the fix