CVE-2026-100684

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH confidence

Score 8.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-26. A secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.1Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Budibase versions 3.41.0 before 3.45.0 contain an authentication bypass in the OIDC/SSO login path of @budibase/server. In sso.authenticate, when no existing user matches the incoming SSO subject, the server looks up pending user invites by the IdP-asserted email address alone — without validating an invite code and without an email_verified check (the email_verified gate protects only the existing-account lookup). An attacker who can register at an IdP that the tenant trusts for OIDC and assert a victim's invited email address (even with email_verified=false) claims the pending invite and inherits all of its granted privileges, including builder and admin.global, with no admin exclusion. This results in takeover of the invited principal and, for admin invites, full tenant compromise (access to all apps, datasources including production credentials, and automations); the invite is consumed, denying onboarding to the legitimate invitee.

CVSS v3
8.1
EG Score
8.1HIGHhigh confidence
EG Risk
52
EG Risk 52/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
24th
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 26, 2026

Last Modified

September 28, 2026

Advisory Details (2)

Auto-updated Sep 26, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

Budibase Server 3.41.0 before 3.45.0 Authentication Bypass via OIDC | Advisories | VulnCheck

https://www.vulncheck.com/advisories/budibase-server-3.41.0-before-3.45.0-authentication-bypass-via-oidc
github Patch Available🟡 PoC Available

Unverified-email OIDC/SSO invite reconcile claims pending invite (up to admin.global) by email alone, no code · Advisory · Budibase/budibase · GitHub

https://github.com/Budibase/budibase/security/advisories/GHSA-35ch-57g2-3g98

Vendor Advisories for CVE-2026-100684(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 30× in last 7d / 36× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-04 09:23 UTCGHSA enrichment
  2. 2026-10-03 22:05 UTCEG score recompute
  3. 2026-10-03 22:05 UTCGHSA enrichment
  4. 2026-10-03 14:25 UTCEPSS rescore
  5. 2026-10-03 10:47 UTCGHSA enrichment
  6. 2026-10-02 23:29 UTCEG score recompute
  7. 2026-10-02 23:28 UTCGHSA enrichment
  8. 2026-10-02 12:09 UTCGHSA enrichment
  9. 2026-10-02 00:49 UTCEG score recompute
  10. 2026-10-02 00:49 UTCGHSA enrichment
  11. 2026-10-01 19:49 UTCEPSS rescore
  12. 2026-10-01 13:27 UTCGHSA enrichment
  13. 2026-10-01 02:09 UTCEG score recompute
  14. 2026-10-01 02:09 UTCGHSA enrichment
  15. 2026-09-30 15:02 UTCEPSS rescore
  16. 2026-09-30 14:51 UTCGHSA enrichment
  17. 2026-09-30 03:33 UTCGHSA enrichment
  18. 2026-09-29 16:16 UTCEG score recompute
  19. 2026-09-29 16:16 UTCGHSA enrichment
  20. 2026-09-29 15:20 UTCEPSS rescore
  21. 2026-09-29 04:57 UTCEG score recompute
  22. 2026-09-29 04:57 UTCGHSA enrichment
  23. 2026-09-28 17:39 UTCEG score recompute
  24. 2026-09-28 17:39 UTCGHSA enrichment
  25. 2026-09-28 16:42 UTCEG score recompute
Show 11 more
  1. 2026-09-28 16:42 UTCGHSA enrichment
  2. 2026-09-28 13:50 UTCEPSS rescore
  3. 2026-09-28 11:44 UTCGHSA enrichment
  4. 2026-09-28 00:26 UTCEG score recompute
  5. 2026-09-28 00:26 UTCGHSA enrichment
  6. 2026-09-27 13:08 UTCGHSA enrichment
  7. 2026-09-27 01:50 UTCEG score recompute
  8. 2026-09-27 01:50 UTCGHSA enrichment
  9. 2026-09-26 14:31 UTCEG score recompute
  10. 2026-09-26 13:35 UTCEG score recompute
  11. 2026-09-26 13:30 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-100684?
CVE-2026-100684 is a high vulnerability published on September 26, 2026. Budibase versions 3.41.0 before 3.45.0 contain an authentication bypass in the OIDC/SSO login path of @budibase/server. In sso.authenticate, when no existing user matches the incoming SSO subject, the server looks up pending user invites by the IdP-asserted email address alone — without validating…
When was CVE-2026-100684 disclosed?
CVE-2026-100684 was first published on September 26, 2026, with the most recent update on September 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-100684 actively exploited?
CVE-2026-100684 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (24th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-100684?
CVE-2026-100684 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-100684?
A fix for CVE-2026-100684 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-100684 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-100684

Explore →

Is Your Infrastructure Affected by CVE-2026-100684?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs