Budibase: OAuth2 Token Disclosure via Automation Test Results Broadcast to Other Builders

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.7 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N

EPSS

• CVE-2026-73308: 0.41% estimated exploitation activity in the next 30 days; percentile 35.06 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary When an SSO-authenticated user tests an automation in the Budibase builder, their OAuth2 access token and refresh token are included in the automation test results. These results are broadcast via WebSocket to all builders connected to the same dev app and stored in an in-memory cache accessible to any builder who polls the test status endpoint. This allows any co-builder of the same app to steal the testing user's OAuth2 tokens. Details The vulnerability exists because getUserContextBindings() intentionally includes OAuth2 tokens in user context bindings (so automations can call external APIs), but the automation test pipeline exposes the full result — including these tokens — to all builders of the same app without sanitization. Step 1: Tokens included in user bindings In packages/server/src/sdk/users/utils.ts:134-161: Step 2: Bindings passed to automation execution In packages/server/src/api/controllers/automation.ts:311-312: Step 3: Tokens placed in trigger outputs In…

Published by the source

24 Jul 2026, 21:25 UTC

Last modified by the source

12 Aug 2026, 19:26 UTC

Source last checked

26 Oct 2026, 13:01 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-gh4h-34gr-87r7

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-gh4h-34gr-87r7

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-73308

Advisory: Budibase: OAuth2 Token Disclosure via Automation Test Results Broadcast to Other Builders
IDs: CVE-2026-73308, GHSA-gh4h-34gr-87r7
Record: https://patchnext.com/advisories/cve-2026-73308 (revision 2, source checked 26 Oct 2026, 13:01 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @budibase/server: affected <= 3.38.1

## Suggested inspection (read-only)
- `npm ls @budibase/server --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @budibase/server.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-gh4h-34gr-87r7 (OSV record GHSA-gh4h-34gr-87r7 lists affected ranges: npm @budibase/server >=0 <=3.38.1)
- Verified: https://github.com/advisories/GHSA-gh4h-34gr-87r7 (GitHub-reviewed advisory GHSA-gh4h-34gr-87r7 lists affected ranges: npm @budibase/server >=0 <=3.38.1)

Commands are suggestions: review each one before running it.