CVE-2026-50137

CRITICALNVD 9.49.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 9.4 from GitHub Security Advisory (severity: HIGH) published 2026-06-22. NVD baseline CVSS 9.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-39913 (ENISA EUVD) · GHSA-35c4-rvc8-frhm (GitHub Security Advisories)Source: ENISA EUVD

9.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.4Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Budibase is an open-source low-code platform. Prior to 3.39.0, an anonymous attacker who knows or can enumerate a workspace id (app_...) and an S3-source datasource id (ds_...) can call this endpoint with no auth and obtain a 15-minute pre-signed PUT URL minted on the victim's IAM identity. The endpoint also returns the publicUrl so the attacker knows exactly where their PUT lands. Because bucket is attacker-controlled, the attacker can write to any bucket those IAM credentials can write to, not only the bucket the datasource was configured for. The Budibase server route POST /api/attachments/:datasourceId/url (packages/server/src/api/routes/static.ts) is registered with only the recaptcha middleware. There is no authorized(...) middleware in the chain. The controller (packages/server/src/api/controllers/static/index.ts::getSignedUploadURL) looks the requested datasource up, instantiates an AWS S3 client with the datasource's stored accessKeyId / secretAccessKey, and returns an AWS Signature V4 pre-signed PutObjectCommand URL for the caller-supplied bucket and key. The bucket is not pinned to the datasource's configured bucket. The workspace context required by sdk.datasources.get is sourced by getWorkspaceIdFromCtx (packages/backend-core/src/utils/utils.ts) from any of: the x-budibase-app-id header, the JSON body appId, a path segment that begins with the workspace prefix, or ?appId=. auth.buildAuthMiddleware([], { publicAllowed: true }) runs before any of this and explicitly allows anonymous requests. The currentWorkspace middleware's "deny access to dev preview" branch only triggers under isBrowser(ctx) && !isApiKey(ctx); isBrowser checks the parsed User-Agent for a recognised browser, so any non-browser client (curl, the supplied PoC, any tool not setting a browser UA) is neither and reaches dev workspaces too. This vulnerability is fixed in 3.39.0.

CVSS v3
9.4
EG Score
9.4CRITICALmedium confidence
EG Risk
58
EG Risk 58/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity94% × 45%
Impact severity (EG Severity): CVSS 9.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
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.4%
EPSS %ILE
35th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.4): severity, escalated by confirmed exploitation. This CVE's 9.4 is its impact severity (EG Severity), not escalated.

EG Severity
9.4 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 22, 2026

Last Modified

June 30, 2026

Advisory Details (1)

Auto-updated Oct 2, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

Budibase: POST /api/attachments/:datasourceId/url is unauthenticated and lets anonymous callers mint S3 PUT pre-signed URLs using stored datasource IAM credentials · Advisory · Budibase/budibase · GitHub

https://github.com/Budibase/budibase/security/advisories/GHSA-35c4-rvc8-frhm

Vendor Advisories for CVE-2026-50137(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npm@budibase/server @ 3.39.0 (fixes < 3.39.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@budibase/server—
  • every version up to 3.39.0: fixed in 3.39.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 60× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 183 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 83 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-50137?
CVE-2026-50137 is a critical-severity vulnerability; its CVE record was published on June 22, 2026. Budibase is an open-source low-code platform. Prior to 3.39.0, an anonymous attacker who knows or can enumerate a workspace id (app_...) and an S3-source datasource id (ds_...) can call this endpoint with no auth and obtain a 15-minute pre-signed PUT URL minted on the victim's IAM identity. The…
When was the CVE record for CVE-2026-50137 published?
The CVE record for CVE-2026-50137 was published on June 22, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 30, 2026; the record at its source may have been updated since.
Is CVE-2026-50137 actively exploited?
CVE-2026-50137 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-50137?
CVE-2026-50137 has a CVSS v3 base score of 9.4 (NVD).
How do I remediate CVE-2026-50137?
A fix for CVE-2026-50137 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-50137 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-50137?

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

Book a Demo →Browse All CVEs