OAuth2 token disclosure via unsanitized metadata responses
Published Aug 13, 2026 · Updated Aug 13, 2026
Information disclosure in Budibase before 3.40.0 allows remote authenticated users with the POWER role to read SSO OAuth2 tokens. The user metadata handlers pass global user objects through processUser(), which removes passwords and roles but leaves oauth2.accessToken and oauth2.refreshToken in both endpoint responses. Exploitation requires a POWER-role account and at least one OIDC- or Google-authenticated user; exposed refresh tokens support persistent access to connected services.
Summary
What happened
Information disclosure in Budibase before 3.40.0 allows remote authenticated users with the POWER role to read SSO OAuth2 tokens. The user metadata handlers pass global user objects through processUser(), which removes passwords and roles but leaves oauth2.accessToken and oauth2.refreshToken in both endpoint responses. Exploitation requires a POWER-role account and at least one OIDC- or Google-authenticated user; exposed refresh tokens support persistent access to connected services.
The record
- CVE
- CVE-2026-73304
- Published
- Aug 13, 2026
- Updated
- Aug 13, 2026
- Vendor
- Budibase
- Product
- Budibase
- Classifications
- CWE-200, T1528
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 13, 2026CVE publishedPublication date reported by the CVE source.
- Aug 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.39.25
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Vendor advisory metadata-endpoint proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo