Budibase backend-core (@budibase/backend-core, as used by @budibase/server) omits the shared address space range 100.64.0.0/10 from its default SSRF blacklist (DEFAULT_BLACKLIST) used by REST datasource query previews. When the default blacklist is active (i.e., a self-hosted deployment has not defined BLACKLIST_IPS), an authenticated user with the Builder permission can submit a REST datasource query preview request to POST /api/queries/preview targeting a reachable HTTP(S) service in the 100.64.0.0/10 range, causing the server to send a request to that target and return its response through the preview flow. Per the advisory, no released fix was identified at the time of publication; remediation is to add 100.64.0.0/10 to DEFAULT_BLACKLIST.
CVE-2026-82241
Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-28. a secondary CVSS source baseline 7.1; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.1
- EG Score
- 7.1(high)
- EG Risk
- 32(Track)EG Risk 32/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 computedSeverity71% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 7%
- KEV
- Not listed
Published
August 28, 2026
Last Modified
August 28, 2026
Advisory Details (2)
Auto-updated Aug 28, 2026Budibase backend-core SSRF via incomplete default blacklist | Advisories | VulnCheck
https://www.vulncheck.com/advisories/budibase-backend-core-ssrf-via-incomplete-default-blacklistBudibase backend-core omits shared address space from its default SSRF blacklist · Advisory · Budibase/budibase · GitHub
https://github.com/Budibase/budibase/security/advisories/GHSA-9754-4wm6-3c8rVendor Advisories for CVE-2026-82241(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 11× in last 7d / 11× 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.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 20:26 UTCGHSA enrichment
- 2026-08-29 07:42 UTCGHSA enrichment
- 2026-08-28 18:57 UTCGHSA enrichment
- 2026-08-28 16:36 UTCEG score recompute
- 2026-08-28 16:36 UTCGHSA enrichment
- 2026-08-28 15:38 UTCEG score recompute
- 2026-08-28 15:38 UTCGHSA enrichment
- 2026-08-28 12:22 UTCEG score recompute
- 2026-08-28 11:23 UTCEG score recompute
- 2026-08-28 11:19 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
- CVE-2016-10927EG 10.0CRITICAL
- CVE-2016-10926EG 10.0CRITICAL
- CVE-2018-10511EG 10.0CRITICAL
- CVE-2018-1000124EG 10.0CRITICAL
- CVE-2017-11291EG 10.0EPSS p91CRITICAL
- CVE-2017-12905EG 10.0CRITICAL
- CVE-2017-8794EG 10.0CRITICAL
- CVE-2017-13667EG 9.9CRITICAL
- CVE-2017-17674EG 9.8CRITICAL
- CVE-2013-4864EG 9.8EPSS p93CRITICAL
Frequently asked(5)
What is CVE-2026-82241?
When was CVE-2026-82241 disclosed?
Is CVE-2026-82241 actively exploited?
What is the CVSS score of CVE-2026-82241?
How do I remediate CVE-2026-82241?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-82241
Is Your Infrastructure Affected by CVE-2026-82241?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.