llamaCVEVulnerability Intelligence
/
Advisory · GitHub · Maven · io.kestra:kestra

GHSA-V3P3-QRVF-JGMR

Dashboard OR filter on JDBC returns other tenants' rows through charts/preview on 1.3.x

Parche disponible
Descargar PNG JSON
CVSS 3.1
5.0
Media
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N Fuente: GitHub
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche1 versiónPrimer parche a -7 d de la divulgación
Exposición18 dDesde la divulgación, 3 nov 2026, 6:25 a. m.
Detección15 dDesde la divulgación hasta su ingreso al índice
Decisión estimadaSeguir
Remediar en la ventana regular de mantenimiento
Estimación de Llama con el árbol SSVC de CISA a partir de vector CVSS 3.1 y la evidencia de explotación (sin evaluación oficial): sin explotación conocida, no automatizable e impacto técnico parcial. Hay versiones corregidas disponibles.
Esto no amerita reunión. Un ticket basta.Tranqui, pero que no se quede en el olvido.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Explotación
Remediación
Parche 1.3.45
Monitoreo
Detectada +1
27 oct 26
3 nov 26
19 nov 26
21 nov 26
27 oct 26
2 nov 26
9 nov 26
15 nov 26
21 nov 26
FechaFaseEventoDetalle
Remediación Parche 1.3.45 io.kestra:kestra · -7 d desde divulgación
Divulgación Publicada GHSA-V3P3-QRVF-JGMR divulgada · CVSS 5 (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
Summary

On JDBC backends, `JdbcFilterService.or()` joins a dashboard `Or` filter to the whole WHERE clause instead of adding it as one condition. The query becomes `(tenant_id = ? AND deleted = false AND <earlier filters>) OR <a> OR <b>`. So a chart with an OR filter returns every row that matches `<a>` or `<b>`, from any tenant and including deleted rows.

On 1.3.x, `POST /api/v1/{tenant}/dashboards/charts/preview` and `charts/export/to-csv` parse the chart without validating it, so any user who can preview a chart can send an OR filter.

2.0 is not affected.

Impact
  • Multi-tenant instances on 1.3.x: a user who can preview a dashboard chart in tenant A can read the Flows, Triggers and Metrics rows of every tenant, including deleted ones.
  • Flows: id, namespace, revision.
  • Triggers: namespace, flow, trigger id, execution id, next date, worker id.
  • Metrics: namespace, flow, execution and task ids, metric name and value.
  • Executions and Logs charts are not affected (from the code, not run): preview always sets a start date (`TimeLineSearch` defaults to 8 days), so `whereWithGlobalFilters` calls `f.getField().equals(...)` on the field-less `Or` and throws a `NullPointerException` before the query runs.
  • OSS (single tenant): only deleted rows show up, and the OR no longer narrows the result.
  • Not checked: whether EE adds RBAC/namespace conditions to the same WHERE. If it does, they are dropped too.
Affected versions and components
  • Component: `jdbc` module, `JdbcFilterService.or()` https://github.com/kestra-io/kestra/blob/939ae36919cdee67ef6040b8d730295c7f04f2e0/jdbc/src/main/java/io/kestra/jdbc/services/JdbcFilterService.java#L137-L142 (v1.3.44). It is unchanged since #6607 (v0.21) and still on develop (L141-L148 https://github.com/kestra-io/kestra/blob/ecb346000e13ab1e43b8b961912c268c309908f1/jdbc/src/main/java/io/kestra/jdbc/services/JdbcFilterService.java#L141-L148).
  • Directly reachable:
  • 1.3.x LTS (checked 1.3.0 and 1.3.44): `buildChartPreviewDataQuery` https://github.com/kestra-io/kestra/blob/939ae36919cdee67ef6040b8d730295c7f04f2e0/webserver/src/main/java/io/kestra/webserver/controllers/api/DashboardController.java#L297-L299 parses the chart and never calls the validator. `charts/export/to-csv` uses the same method.
  • Also 1.2.x and 1.0.60 (both out of support). In 1.0.x a field-less `Or` also passes validation, since `AbstractFilter.field` only became `@NotNull` in #12822 (v1.2.0).
  • 2.0.x: `charts/preview` and `charts/export` now validate the chart. That came with 77e7427cb (the REGEX ReDoS fix, 2026-07-10), and no `Or` passes validation there.
  • Two things remain on 2.0:
  • `buildDashboardChardDataQuery` still runs stored charts without validating them, so a dashboard saved on ≤1.1 with a field-less `Or` would still hit this on 2.0 EE;
  • the code bug itself.
  • Backends: H2 tested. Postgres and MySQL use the same `JdbcFilterService`. Elasticsearch (EE) not checked.
Steps to reproduce (PoC)

On a multi-tenant 1.3.x instance, as a user of tenant A, with a flow in tenant B whose namespace is `company.shared`:

POST /api/v1/<tenant-a>/dashboards/charts/preview
Content-Type: application/json

{"chart": "id: flows\ntype: io.kestra.plugin.core.dashboard.chart.Table\ndata:\n  type: io.kestra.plugin.core.dashboard.data.Flows\n  columns:\n    id:\n      field: ID\n  where:\n    - type: OR\n      values:\n        - field: NAMESPACE\n          type: EQUAL_TO\n          value: company.shared\n        - field: NAMESPACE\n          type: EQUAL_TO\n          value: company.nothing\n"}

The response lists tenant B's flow. The same chart with a plain `field: NAMESPACE, type: EQUAL_TO` filter lists only tenant A's flows.

I ran this as a `DashboardControllerTest` on v1.3.44 (OSS, H2), through the real preview route, as tenant `main`. The data: flow `mine` in `main`, flow `deleted` in `main` (then deleted), and flow `theirs` in a second tenant, all in one namespace.

  • Plain filter `namespace = X`: `main_X_deleted_1`, `main_X_mine_1`
  • `namespace = X OR namespace = Y`: `main_X_deleted_1`, `main_X_deleted_2`, `main_X_mine_1`, `othertenant…_X_theirs_1`

The same check against the repository on develop (`flowRepository.fetchData(tenantA, …)` with an `Or`) also returns the other tenant's flow and the deleted revision. I can share both tests.

Details
  • `or()` https://github.com/kestra-io/kestra/blob/939ae36919cdee67ef6040b8d730295c7f04f2e0/jdbc/src/main/java/io/kestra/jdbc/services/JdbcFilterService.java#L137-L142 calls `orQuery.or(...)` on the select step. `orCondition()` in the same class builds the OR as one condition, the right way.
  • jOOQ renders it on H2 as: `where ((("tenant_id" = 'tenant-a' and "deleted" = false) or "namespace" = 'ns1' or "namespace" = 'ns2') and ...)`.
  • A second bug in the same class: since #17457 (v2.0.0), `inCondition()` returns `notIn` (and `QueryFilter.Op.NOT_IN` for labels). So an `IN` inside an `Or` matches the opposite rows.
  • Also on 2.0: every OR filter is rejected (`field` is `@NotNull`, while `OrFilterValidator` forbids a `field` on an `Or`), although the docs describe `type: OR`. Allowing `Or` there again without fixing `or()` would reopen this.
Severity (my assessment)

Medium for multi-tenant 1.3.x: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N` (5.0). This is metadata, not credentials. It is higher if EE's RBAC conditions are in the same WHERE.

Fix
  • `or()`: `return query.and(orCondition(fieldsMapping, filter));`
  • `inCondition()`: `field(field).in(...)` and `QueryFilter.Op.IN` for labels.
  • 1.3.x: validate the chart in `charts/preview` and `charts/export/to-csv`, as 2.0 does.
  • Validate stored charts before rendering them.
Disclosure and credit

I won't post anything about this publicly until you say so. I'm glad to help with the fix, for example in a temporary private fork. Credit as kruxarth is fine.

Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.

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:C
CambiadoSin cambio
ConfidencialidadC:L
AltoBajoNinguno
IntegridadI:N
AltoBajoNinguno
DisponibilidadA:N
AltoBajoNinguno
Score de explotaciónQué tan fácil y probable es que la exploten
8.7/ 10Muy alto
Vector 8.7 (muy fácil) · sin evidencia de explotación.
Versiones

Rangos afectados

Afectada Corregida Última
io.kestra:kestra≤ 1.3.44
1.3.44
2.0.10
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
mavenio.kestra:kestra
Corregida 1.3.45 -7 d 2.0.10 no afectada
Versiones corregidas1.3.45
Explotación

Arsenal público

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

Referencias
Advisoryhttps://github.com/kestra-io/kestra/security/advisories/GHSA-v3p3-qrvf-jgmr

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