Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-100684 – Authentication Bypass / Privilege Escalation via OIDC SSO – Budibase Server 3.41.0

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-100684 is a critical improper authentication vulnerability (CWE-287) in the OIDC/SSO login flow of Budibase Server. Because the server resolves pending user invites by matching only the identity-provider-asserted email address — without validating an invite code or requiring the email to be verified — a remote, unauthenticated attacker who controls an account at a trusted identity provider can claim another user’s pending invite and inherit its privileges, up to global administrator. The issue affects Budibase Server 3.41.0 through 3.44.x and carries a CVSS score of 9.2.

Technical details

  • Root cause: in the sso.authenticate logic, when no existing local user matches the incoming SSO subject, the server falls back to looking up pending invites by the IdP-asserted email address alone.
  • The email-verification check (email_verified) that gates lookups against existing accounts is not applied to this invite-matching path, so an unverified email assertion is sufficient.
  • Trigger conditions: the target tenant must have OIDC/SSO login enabled and trust an identity provider the attacker can register with (or otherwise assert an arbitrary/victim email through).
  • Attack vector: Network — the attacker completes the standard OIDC login/callback flow against the Budibase instance, asserting a victim’s invited email address.
  • Impact: the attacker claims and consumes the victim’s pending invite, inheriting its granted role — including builder or global admin — resulting in account takeover and, for administrative invites, full tenant compromise (access to all apps, datasources with stored production credentials, and automations). The legitimate invitee is simultaneously locked out since the invite is consumed.

Affected software

  • Budibase Server (@budibase/server) versions 3.41.0 up to (but not including) 3.45.0

Severity

  • CVSS v3.1 Base Score: 8.1 (High) — CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
  • CVSS v4.0 Score: 9.2 (Critical) — CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade Budibase Server to version 3.45.0 or later, which fixes the invite-matching logic.
  • If patching cannot happen immediately: disable OIDC/SSO login for the tenant until the upgrade is applied, and audit pending invites and any accounts created during the affected window for signs of unauthorized invite claims.
  • After upgrading, review global admin and builder role assignments to confirm no unexpected accounts inherited elevated privileges while the instance was vulnerable.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge