llamaCVEVulnerability Intelligence
/
Advisory · GitHub · npm · @budibase/server

GHSA-9754-4WM6-3C8R

Budibase backend-core omits shared address space from its default SSRF blacklist

Sin parche publicado
Descargar PNG JSON
CVSS 3.1
7.1
Alta
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N Fuente: GitHub
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
ParcheSin parcheEl fabricante no ha publicado corrección
Exposición97 dDesde la divulgación, 14 ago 2026, 3:57 a. m.
Detección96 dDesde la divulgación hasta su ingreso al índice
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Explotación
Remediación
Monitoreo
Detectada +1
14 ago 26
18 nov 26
19 nov 26
14 ago 26
7 sept 26
2 oct 26
26 oct 26
19 nov 26
FechaFaseEventoDetalle
Divulgación Publicada GHSA-9754-4WM6-3C8R divulgada · CVSS 7.1 (GitHub)
Monitoreo Detectada Ingresó al índice
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Descripción del advisory
Texto original · GitHub · en inglés

Affected product

`@budibase/backend-core` as used by Budibase REST datasource query previews through `POST /api/queries/preview`, when the default blacklist is active.

Summary

`DEFAULT_BLACKLIST` omits `100.64.0.0/10`. A Builder can use a REST datasource query preview to cause the Budibase server to send HTTP(S) requests to a reachable target in that range and return its response through the preview flow.

The default blacklist is active unless a self-hosted deployment defines `BLACKLIST_IPS`.

Technical details

`packages/backend-core/src/blacklist/blacklist.ts` defines `DEFAULT_BLACKLIST`, builds it in `refreshBlacklist`, and checks resolved addresses in `isBlacklisted`. None of its configured CIDRs cover `100.64.0.0/10`.

`packages/backend-core/src/utils/outboundFetch.ts` resolves each request target in `resolveSafePinnedIp` and rejects it only when `isBlacklisted` returns true. `packages/server/src/integrations/rest.ts` calls `fetchWithBlacklist` for REST integration requests.

`packages/server/src/api/routes/query.ts` mounts `POST /api/queries/preview` on `builderRoutes`. The permission test confirms a non-Builder request receives `403`.

Preconditions

  • An authenticated user has the `BUILDER` permission.
  • The user can preview a REST datasource in the relevant workspace.
  • The Budibase server can reach an HTTP(S) target in `100.64.0.0/10`.
  • The default blacklist is active; a self-hosted deployment has not defined `BLACKLIST_IPS`.

Verification

  1. Create controlled marker endpoints reachable only from the Budibase server: one at `<rfc1918-target>` and one at `<shared-address-target>` within `100.64.0.0/10`.
  2. Authenticate as a Builder and submit otherwise equivalent valid REST read-preview requests to `POST /api/queries/preview`. The payload must include `datasourceId`, `queryVerb`, `fields`, `schema`, and an empty `parameters` array as applicable.
  3. Control: configure the REST datasource for `<rfc1918-target>`. The preview should fail with HTTP `400` before the outbound request.
  4. Bypass: configure the REST datasource for `<shared-address-target>`. Confirm receipt of the outbound request at the controlled endpoint and confirm that its response is returned by the preview.

Impact

A Builder can make the Budibase server access reachable HTTP(S) services in `100.64.0.0/10` and receive their responses through query preview. This does not establish access to other private ranges, cloud metadata services, cross-tenant data, or host-level execution.

Affected versions

The default blacklist was introduced in released `@budibase/backend-core` version `3.33.4`. Version `3.39.32`, the latest verified release, still omits `100.64.0.0/10`. No released fix was identified.

This range scopes the incomplete default blacklist introduced in `3.33.4`; it does not assess the different blacklist implementation in earlier releases.

Remediation

Add `100.64.0.0/10` to `DEFAULT_BLACKLIST`, or replace the deny-list with a policy that explicitly permits intended outbound destinations.

Add regression tests that assert addresses in this range are blocked when the default blacklist is active, and an integration test showing that REST query preview rejects such a target before an outbound request is sent.

Evidence

  • Commit `62f50d9779cbd7673bc5b1d99e167f3d2e175ec1`, included in merged PR #18236, introduced `DEFAULT_BLACKLIST`.
  • The `3.33.4` release contains that implementation.
  • Source at released version `3.39.32` still lacks `100.64.0.0/10`.
  • The NPM registry contains matching `@budibase/backend-core` versions `3.33.4` and `3.39.32`.
Vector CVSS 3.1

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · GitHub
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:L
BajaAlta
PrivilegiosPR:L
NingunoBajosAltos
InteracciónUI:N
NingunaRequerida
AlcanceS:U
CambiadoSin cambio
ConfidencialidadC:H
AltoBajoNinguno
IntegridadI:L
AltoBajoNinguno
DisponibilidadA:N
AltoBajoNinguno
Versiones

Rangos afectados

Afectada Corregida Última
@budibase/server< 3.41.3
3.38.1
3.41.3
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
npm@budibase/server
Sin parche — — 3.38.1 afectada
Versiones corregidas3.41.3
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Advisoryhttps://github.com/Budibase/budibase/security/advisories/GHSA-9754-4wm6-3c8r

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.