CVE-2026-45717

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.3%, 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, nvd
Elevated
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 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.38.1, Budibase exposes a REST API for datasource management. The route PUT /api/datasources/:datasourceId is registered in the authorizedRoutes group with TABLE/READ permission. This is the same authorization level as the read endpoint (GET /api/datasources/:datasourceId). Every authenticated Budibase app user with the BASIC built-in role or higher carries TABLE/WRITE (and therefore TABLE/READ) permissions, and the datasource update controller performs no additional builder check. As a result, any authenticated non-builder app user can submit a PUT request to rewrite a datasource's config object — including the connection host, port, database credentials, or the base url of a REST datasource. Because no network-level SSRF protection is applied to SQL driver connections, redirecting a PostgreSQL/MySQL/MongoDB datasource to an internal IP address succeeds and the attacker can probe or interact with internal services on arbitrary ports. This vulnerability is fixed in 3.38.1.

CVSS v3
8.8
EG Score
8.8(medium)
EPSS
16.4%
KEV
Not listed

Published

May 15, 2026

Last Modified

May 27, 2026

Advisory Details (2)

Auto-updated Jun 2, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github.
github Patch Available🟡 PoC Available

`PUT /api/datasources/:datasourceId` is protected only by `TABLE/READ` permission instead of builder access, allowing any authenticated app user to overwrite datasource connection parameters including host, port, and URL. · Advisory · Budibase/budibase · GitHub

https://github.com/Budibase/budibase/security/advisories/GHSA-44m2-crh7-f4q2
github_release Patch Available

3.38.1

Patch available: Budibase/budibase 3.38.1

https://github.com/Budibase/budibase/releases/tag/3.38.1

Vendor Advisories for CVE-2026-45717(1)

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

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
@budibase/server—3.38.1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 53× 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.

Showing the most recent 100 of 102 total refreshes for this CVE.

  1. 2026-07-12 05:46 UTCEPSS rescore
  2. 2026-07-11 08:27 UTCEPSS rescore
  3. 2026-07-09 19:10 UTCEPSS rescore
  4. 2026-07-08 15:16 UTCEPSS rescore
  5. 2026-07-07 13:46 UTCEPSS rescore
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-05 02:30 UTCEPSS rescore
  9. 2026-07-04 06:31 UTCEPSS rescore
  10. 2026-07-01 15:07 UTCEPSS rescore
  11. 2026-06-30 23:22 UTCEPSS rescore
  12. 2026-06-29 21:28 UTCEG score recompute
  13. 2026-06-29 14:06 UTCEPSS rescore
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-28 14:07 UTCEPSS rescore
  16. 2026-06-28 09:29 UTCEG score recompute
  17. 2026-06-28 04:56 UTCEPSS rescore
  18. 2026-06-28 04:56 UTCEPSS rescore
  19. 2026-06-27 21:52 UTCEG score recompute
  20. 2026-06-27 07:50 UTCEG score recompute
  21. 2026-06-27 03:08 UTCEPSS rescore
  22. 2026-06-26 20:11 UTCEG score recompute
  23. 2026-06-25 18:45 UTCEG score recompute
  24. 2026-06-25 13:49 UTCEPSS rescore
  25. 2026-06-24 14:05 UTCEPSS rescore
Show 75 more
  1. 2026-06-23 21:33 UTCEPSS rescore
  2. 2026-06-23 21:33 UTCEPSS rescore
  3. 2026-06-22 14:25 UTCEPSS rescore
  4. 2026-06-22 14:25 UTCEPSS rescore
  5. 2026-06-21 14:56 UTCEPSS rescore
  6. 2026-06-21 14:56 UTCEPSS rescore
  7. 2026-06-21 01:59 UTCEPSS rescore
  8. 2026-06-21 01:59 UTCEPSS rescore
  9. 2026-06-19 19:26 UTCEPSS rescore
  10. 2026-06-19 19:26 UTCEPSS rescore
  11. 2026-06-18 17:52 UTCEPSS rescore
  12. 2026-06-18 17:52 UTCEPSS rescore
  13. 2026-06-18 03:55 UTCEG score recompute
  14. 2026-06-17 17:53 UTCEPSS rescore
  15. 2026-06-17 13:23 UTCEG score recompute
  16. 2026-06-16 22:48 UTCEG score recompute
  17. 2026-06-16 17:52 UTCEPSS rescore
  18. 2026-06-16 11:10 UTCEG score recompute
  19. 2026-06-15 23:32 UTCEG score recompute
  20. 2026-06-15 17:49 UTCEPSS rescore
  21. 2026-06-14 22:32 UTCEG score recompute
  22. 2026-06-14 10:54 UTCEG score recompute
  23. 2026-06-13 23:17 UTCEG score recompute
  24. 2026-06-13 23:00 UTCEPSS rescore
  25. 2026-06-13 08:18 UTCEG score recompute
  26. 2026-06-12 23:12 UTCEPSS rescore
  27. 2026-06-12 23:12 UTCEPSS rescore
  28. 2026-06-12 20:39 UTCEG score recompute
  29. 2026-06-12 09:01 UTCEG score recompute
  30. 2026-06-11 21:19 UTCEG score recompute
  31. 2026-06-11 14:00 UTCEPSS rescore
  32. 2026-06-11 09:42 UTCEG score recompute
  33. 2026-06-10 22:18 UTCEPSS rescore
  34. 2026-06-10 22:05 UTCEG score recompute
  35. 2026-06-10 13:22 UTCEPSS rescore
  36. 2026-06-10 13:22 UTCEPSS rescore
  37. 2026-06-10 10:27 UTCEG score recompute
  38. 2026-06-09 22:47 UTCEG score recompute
  39. 2026-06-09 11:10 UTCEG score recompute
  40. 2026-06-08 23:33 UTCEG score recompute
  41. 2026-06-08 14:17 UTCEPSS rescore
  42. 2026-06-08 14:17 UTCEPSS rescore
  43. 2026-06-08 11:55 UTCEG score recompute
  44. 2026-06-08 00:17 UTCEG score recompute
  45. 2026-06-07 15:25 UTCEPSS rescore
  46. 2026-06-07 15:25 UTCEPSS rescore
  47. 2026-06-07 12:40 UTCEG score recompute
  48. 2026-06-07 01:03 UTCEG score recompute
  49. 2026-06-06 13:47 UTCEPSS rescore
  50. 2026-06-06 13:47 UTCEPSS rescore
  51. 2026-06-06 13:25 UTCEG score recompute
  52. 2026-06-06 01:47 UTCEG score recompute
  53. 2026-06-05 22:47 UTCEPSS rescore
  54. 2026-06-05 14:10 UTCEG score recompute
  55. 2026-06-05 06:10 UTCEPSS rescore
  56. 2026-06-05 06:10 UTCEPSS rescore
  57. 2026-06-05 02:33 UTCEG score recompute
  58. 2026-06-04 14:55 UTCEG score recompute
  59. 2026-06-04 13:12 UTCEPSS rescore
  60. 2026-06-04 13:12 UTCEPSS rescore
  61. 2026-06-04 03:18 UTCEG score recompute
  62. 2026-06-03 15:41 UTCEG score recompute
  63. 2026-06-03 04:03 UTCEG score recompute
  64. 2026-06-02 20:13 UTCEPSS rescore
  65. 2026-06-02 16:25 UTCEG score recompute
  66. 2026-06-02 04:47 UTCEG score recompute
  67. 2026-06-01 17:09 UTCEG score recompute
  68. 2026-06-01 13:52 UTCEPSS rescore
  69. 2026-06-01 13:52 UTCEPSS rescore
  70. 2026-06-01 05:32 UTCEG score recompute
  71. 2026-05-31 22:30 UTCEPSS rescore
  72. 2026-05-31 22:30 UTCEPSS rescore
  73. 2026-05-29 13:44 UTCEPSS rescore
  74. 2026-05-29 13:44 UTCEPSS rescore
  75. 2026-05-28 13:44 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-45717?
CVE-2026-45717 is a high vulnerability published on May 15, 2026. Budibase is an open-source low-code platform. Prior to 3.38.1, Budibase exposes a REST API for datasource management. The route PUT /api/datasources/:datasourceId is registered in the authorizedRoutes group with TABLE/READ permission. This is the same authorization level as the read endpoint (GET…
When was CVE-2026-45717 disclosed?
CVE-2026-45717 was first published in the National Vulnerability Database on May 15, 2026, with the most recent update on May 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45717 actively exploited?
CVE-2026-45717 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 16.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-45717?
CVE-2026-45717 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-45717?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45717, 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-45717

Explore →

Is Your Infrastructure Affected by CVE-2026-45717?

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

Start Free Scan →Browse All CVEs