CVE-2026-73308 Budibase: OAuth2 Token Disclosure via Automation Test Results Broadcast to Other Builders
A co-builder can obtain another user's OAuth2 tokens via unscoped automation test results, potentially leading to account takeover.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2026-73308?
CVE-2026-73308 is a medium-severity vulnerability in budibase, published on 12 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official description
Budibase is an open-source low-code platform. Prior to 3.39.25, packages/server/src/api/controllers/automation.ts returned automation test results containing trigger.outputs.user.oauth2, broadcast BuilderSocketEvent.AutomationTestProgress to the app room, and stored progress in packages/server/src/automations/testProgress.ts without user scoping. A co-builder could receive or poll another SSO-authenticated builder test and obtain OAuth2 access and refresh tokens. The fix adds sanitizeAutomationTestResult and isolates progress by user. This issue is fixed in version 3.39.25.
Weakness: CWE-200
Which versions are affected by CVE-2026-73308?
2 open source packages ship an affected version, including @budibase/server.
| Package | Affected | Fixed in |
|---|---|---|
@budibase/server npm | All versions to 3.38.1 | None |
@budibase/server npm | All versions to 3.38.1 | None |
How do I fix CVE-2026-73308?
No fix has been published for CVE-2026-73308 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-73308 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73308 exists.
Sources
Also known as GHSA-gh4h-34gr-87r7.