Budibase up to 3.39.29 OIDC Flow oidc.ts users.getGlobalUserByEmail assertion
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 1.98 |
Summary
A vulnerability identified as critical has been detected in Budibase up to 3.39.29. This impacts the function users.getGlobalUserByEmail of the file packages/backend-core/src/middleware/passport/sso/oidc.ts of the component OIDC Flow. Performing a manipulation results in assertion.
This vulnerability is reported as CVE-2026-73302. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability, which was classified as critical, was found in Budibase up to 3.39.29. This affects the function users.getGlobalUserByEmail of the file packages/backend-core/src/middleware/passport/sso/oidc.ts of the component OIDC Flow. The manipulation with an unknown input leads to a assertion vulnerability. CWE is classifying the issue as CWE-617. The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Budibase is an open-source low-code platform. Prior to 3.39.30, the OIDC flow in packages/backend-core/src/middleware/passport/sso/oidc.ts resolved an email without getEmailVerified or an email_verified requirement, and packages/backend-core/src/middleware/passport/sso/sso.ts then used users.getGlobalUserByEmail as a fallback account-linking key. An attacker who can authenticate through a configured identity provider that asserts a victim email as unverified can have a fresh provider identity merged into the victim Budibase account and inherit the victim roles. This issue is fixed in version 3.39.30.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-73302 since 08/11/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details are known, but no exploit is available.
Upgrading to version 3.39.30 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
- 3.39.0
- 3.39.1
- 3.39.2
- 3.39.3
- 3.39.4
- 3.39.5
- 3.39.6
- 3.39.7
- 3.39.8
- 3.39.9
- 3.39.10
- 3.39.11
- 3.39.12
- 3.39.13
- 3.39.14
- 3.39.15
- 3.39.16
- 3.39.17
- 3.39.18
- 3.39.19
- 3.39.20
- 3.39.21
- 3.39.22
- 3.39.23
- 3.39.24
- 3.39.25
- 3.39.26
- 3.39.27
- 3.39.28
- 3.39.29
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AssertionCWE: CWE-617
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Budibase 3.39.30
Timeline
08/11/2026 CVE reserved08/13/2026 VulDB entry created
08/14/2026 Advisory disclosed
08/14/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-73302 (🔒)
GCVE (CVE): GCVE-0-2026-73302
GCVE (VulDB): GCVE-100-389937
Entry
Created: 08/14/2026 00:40Changes: 08/14/2026 00:40 (56)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.