CVE-2026-100683

HIGHPre-NVD 8.08.0—
EchelonGraph scoreHIGH confidence

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

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

A fix is available — apply it.

Budibase (@budibase/server) before 3.45.0 builds MySQL and MSSQL column-rename DDL in packages/backend-core/src/sql/sqlTable.ts by interpolating identifiers directly into a raw query string (backtick-quoted for MySQL, a single-quoted sp_rename literal for MSSQL) without applying the project's quoteMySqlIdentifier / quoteSqlServerIdentifier helpers. An attacker with DDL rights on a connected MySQL/MSSQL datasource can create a column whose name contains a backtick (MySQL) or single quote (MSSQL) plus additional SQL; Budibase's schema introspection stores the name verbatim, and when a Budibase builder later renames that column through the UI (POST /api/tables with _rename.old), the embedded quote character terminates the identifier and the injected SQL is executed. Because the MySQL connection is opened with multipleStatements: true, stacked statements run as Budibase's datasource user, allowing arbitrary reads, writes, or destructive operations on the connected database outside Budibase's row/table permission model. Fixed in 3.45.0.

CVSS v3
8.0
EG Score
8.0HIGHhigh 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
Severity80% × 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.2%
EPSS %ILE
9th
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 before 3.45.0 SQL Injection via column-rename DDL | Advisories | VulnCheck

https://www.vulncheck.com/advisories/budibase-before-3.45.0-sql-injection-via-column-rename-ddl
github Patch Available🟡 PoC Available

Second-order SQL identifier injection in MySQL/MSSQL column-rename DDL (sqlTable.ts) bypassing quote helpers · Advisory · Budibase/budibase · GitHub

https://github.com/Budibase/budibase/security/advisories/GHSA-ppj8-hmx2-m546

Vendor Advisories for CVE-2026-100683(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 33× in last 7d / 41× 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-05 05:47 UTCEG score recompute
  2. 2026-10-05 05:47 UTCGHSA enrichment
  3. 2026-10-04 23:21 UTCEPSS rescore
  4. 2026-10-04 17:50 UTCGHSA enrichment
  5. 2026-10-04 05:53 UTCGHSA enrichment
  6. 2026-10-03 17:57 UTCEG score recompute
  7. 2026-10-03 17:57 UTCGHSA enrichment
  8. 2026-10-03 14:25 UTCEPSS rescore
  9. 2026-10-03 05:59 UTCGHSA enrichment
  10. 2026-10-02 18:03 UTCEG score recompute
  11. 2026-10-02 18:03 UTCGHSA enrichment
  12. 2026-10-02 06:07 UTCEG score recompute
  13. 2026-10-02 06:07 UTCGHSA enrichment
  14. 2026-10-01 19:49 UTCEPSS rescore
  15. 2026-10-01 18:10 UTCGHSA enrichment
  16. 2026-10-01 06:09 UTCGHSA enrichment
  17. 2026-09-30 18:14 UTCEG score recompute
  18. 2026-09-30 18:13 UTCGHSA enrichment
  19. 2026-09-30 15:02 UTCEPSS rescore
  20. 2026-09-30 06:11 UTCGHSA enrichment
  21. 2026-09-29 18:14 UTCEG score recompute
  22. 2026-09-29 18:14 UTCGHSA enrichment
  23. 2026-09-29 15:20 UTCEPSS rescore
  24. 2026-09-29 06:17 UTCEG score recompute
  25. 2026-09-29 06:17 UTCGHSA enrichment
Show 16 more
  1. 2026-09-28 18:21 UTCEG score recompute
  2. 2026-09-28 18:21 UTCGHSA enrichment
  3. 2026-09-28 18:05 UTCEG score recompute
  4. 2026-09-28 18:05 UTCGHSA enrichment
  5. 2026-09-28 16:58 UTCGHSA enrichment
  6. 2026-09-28 14:16 UTCEG score recompute
  7. 2026-09-28 14:16 UTCGHSA enrichment
  8. 2026-09-28 13:50 UTCEPSS rescore
  9. 2026-09-28 02:20 UTCGHSA enrichment
  10. 2026-09-27 14:24 UTCEG score recompute
  11. 2026-09-27 14:24 UTCGHSA enrichment
  12. 2026-09-27 02:29 UTCEG score recompute
  13. 2026-09-27 02:29 UTCGHSA enrichment
  14. 2026-09-26 14:32 UTCEG score recompute
  15. 2026-09-26 13:36 UTCEG score recompute
  16. 2026-09-26 13:30 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-100683?
CVE-2026-100683 is a high vulnerability published on September 26, 2026. Budibase (@budibase/server) before 3.45.0 builds MySQL and MSSQL column-rename DDL in packages/backend-core/src/sql/sqlTable.ts by interpolating identifiers directly into a raw query string (backtick-quoted for MySQL, a single-quoted sprename literal for MSSQL) without applying the project's…
When was CVE-2026-100683 disclosed?
CVE-2026-100683 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-100683 actively exploited?
CVE-2026-100683 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-100683?
CVE-2026-100683 has a CVSS base score of 8.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-100683?
A fix for CVE-2026-100683 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-100683 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-100683?

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

Book a Demo →Browse All CVEs