CVE-2026-31818

CRITICALNVD 9.99.9
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.9 under NVD CVSS v3. EPSS exploit probability: 0.4% (31st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated

Also known asEUVD-2026-18792 (ENISA EUVD)Source: ENISA EUVD

9.9EG
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.9Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Budibase is an open-source low-code platform. Prior to version 3.33.4, a server-side request forgery (SSRF) vulnerability exists in Budibase's REST datasource connector. The platform's SSRF protection mechanism (IP blacklist) is rendered completely ineffective because the BLACKLIST_IPS environment variable is not set by default in any of the official deployment configurations. When this variable is empty, the blacklist function unconditionally returns false, allowing all requests through without restriction. This issue has been patched in version 3.33.4.

CVSS v3
9.9
EG Score
9.9CRITICALmedium confidence
EG Risk
61
EG Risk 61/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)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 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
31st
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.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

EG Severity
9.9 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). 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: 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.

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

April 3, 2026

Last Modified

October 6, 2026

Advisory Details (4)

Auto-updated Oct 28, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
GitHub advisoryMentions a patch (unverified)

Server-Side Request Forgery via REST Connector with Empty Default Blacklist · Advisory · Budibase/budibase · GitHub

Affected: v2.4.3) —

https://github.com/Budibase/budibase/security/advisories/GHSA-7r9j-r86q-7g45
GitHub release Patch Available

3.33.4

Patch available: Budibase/budibase 3.33.4

https://github.com/Budibase/budibase/releases/tag/3.33.4
GitHub pull request Patch Available

fix: block internal REST targets by default

Patch available: Budibase/budibase v3.46.0 (PR #18236 merged 2026-03-13)

https://github.com/Budibase/budibase/pull/18236
GitHub commit Patch Available

commit 5b0fe83d4ece (Budibase/budibase)

Patch available: Budibase/budibase v3.46.0 (contains commit 5b0fe83d4ece)

https://github.com/Budibase/budibase/commit/5b0fe83d4ece52696b62589cba89ef50cc009732

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@budibase/backend-core—
  • every version up to 3.33.4: fixed in 3.33.4
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 52× 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 95 of 234 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. 5 repeat rows among the latest 100 are merged into the row they repeat. The 139 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-31818?
CVE-2026-31818 is a critical-severity vulnerability; its CVE record was published on April 3, 2026. Budibase is an open-source low-code platform. Prior to version 3.33.4, a server-side request forgery (SSRF) vulnerability exists in Budibase's REST datasource connector. The platform's SSRF protection mechanism (IP blacklist) is rendered completely ineffective because the BLACKLIST_IPS environment…
When was the CVE record for CVE-2026-31818 published?
The CVE record for CVE-2026-31818 was published on April 3, 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 October 6, 2026; the record at its source may have been updated since.
Is CVE-2026-31818 actively exploited?
CVE-2026-31818 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-31818?
CVE-2026-31818 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2026-31818?
A fix for CVE-2026-31818 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-31818?

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

Book a Demo →Browse All CVEs