Quick answers
- Is CVE-2026-73308 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-73308 being exploited in the wild.
- How severe is CVE-2026-73308?
- 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-73308?
- A patch was published on 2026-07-22: Version 3.40.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-73308 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-73308?
- 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
This is an information disclosure vulnerability in the automation test pipeline. The root cause is that OAuth2 tokens are intentionally included in user context bindings passed to automations (so they can call external APIs), but the full result—including these sensitive tokens—is broadcast via WebSocket to all builders in the app room and stored in an in-memory cache queryable by any builder via GET /api/automations/:id/test/status. No user isolation or sanitization is applied. Attack requires builder-level access to the same app and that a co-builder authenticates via SSO/OIDC. The attacker can passively receive tokens by keeping the builder UI open, or actively poll the test status endpoint. Tokens remain accessible for 5 minutes. Patched in version 3.40.0 with sanitization of OAuth2 tokens from test results before broadcast/storage.
Affected products
- Budibase @budibase/server <3.40.0
Identifiers
- CVE-2026-73308
- GHSA-gh4h-34gr-87r7
Timeline
- 2026-07-24: disclosed
- 2026-07-22: patched: Version 3.40.0