CVE-2026-64657

HIGHPre-NVD 8.48.4—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 84% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
8.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.4Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Budibase is an open-source low-code platform. Prior to 3.39.19, the PostgreSQL datasource connector in packages/server/src/integrations/postgres.ts interpolates the user-controlled schema configuration field into a SET search_path statement without escaping embedded double quotes, allowing an authenticated administrator who saves or tests the datasource to execute arbitrary SQL through the simple query protocol. This issue is fixed in version 3.39.19.

CVSS v3
8.4
EG Score
8.4(medium)
EG Risk
54(Track*)
EG Risk 54/100SSVC: Track*

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
Severity84% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

August 17, 2026

Last Modified

August 18, 2026

Advisory Details (2)

Auto-updated Aug 17, 2026
Patch available. Sources: github, github_commit.
github_commit Patch Available

commit 67572a82c385 (Budibase/budibase)

Patch available: Budibase/budibase 3.39.18 (contains commit 67572a82c385)

https://github.com/Budibase/budibase/commit/67572a82c3850964f388bfd969779dc025a80224
github Patch Available

PostgreSQL SET search_path SQL Injection in Database Connector · Advisory · Budibase/budibase · GitHub

https://github.com/Budibase/budibase/security/advisories/GHSA-qqf5-x7mj-v43p

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
budibase—3.39.19—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 12× 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-08-22 10:19 UTCEG score recompute
  2. 2026-08-21 23:49 UTCEPSS rescore
  3. 2026-08-21 08:44 UTCEG score recompute
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-19 18:21 UTCEG score recompute
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-18 16:46 UTCEG score recompute
  8. 2026-08-18 15:46 UTCEG score recompute
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-17 21:31 UTCEG score recompute
  11. 2026-08-17 20:30 UTCEG score recompute
  12. 2026-08-17 20:29 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-64657?
CVE-2026-64657 is a high vulnerability published on August 17, 2026. Budibase is an open-source low-code platform. Prior to 3.39.19, the PostgreSQL datasource connector in packages/server/src/integrations/postgres.ts interpolates the user-controlled schema configuration field into a SET search_path statement without escaping embedded double quotes, allowing an…
When was CVE-2026-64657 disclosed?
CVE-2026-64657 was first published in the National Vulnerability Database on August 17, 2026, with the most recent update on August 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64657 actively exploited?
CVE-2026-64657 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 84.1% of all scored CVEs.
What is the CVSS score of CVE-2026-64657?
CVE-2026-64657 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-64657?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64657, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64657

Explore →

Is Your Infrastructure Affected by CVE-2026-64657?

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

Start Free Scan →Browse All CVEs