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

GHSA-4CPW-CP2H-QH6Q

MySQL case-insensitive collation conflates differently-cased namespaces, flows, KV keys and trigger state (potential namespace/tenant isolation bypass in EE)

Parche disponible
Descargar PNG JSON
CVSS 3.1
4.2
Media
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/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:26 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.
Ponle etiqueta y a la cola. Ordenadito.Revisa, agenda, parchea. El clásico de siempre.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Explotación
Remediación
Parche 2.0.8
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 2.0.8 io.kestra:kestra · -7 d desde divulgación
Divulgación Publicada GHSA-4CPW-CP2H-QH6Q divulgada · CVSS 4.2 (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 the MySQL backend, the flows, triggers and kv_metadata tables use the case-insensitive collation utf8mb4_unicode_ci,
so identifiers — including the namespace column — that differ only by letter case resolve to the same record. Writing under
one casing overwrites/hides the other. Proven at the data layer: differently-cased NAMESPACES are conflated (see PoC). Because
Kestra's access model treats namespaces as case-sensitive strings, this is a plausible namespace/tenant isolation bypass in
editions with namespace access control (EE) — the same class as the published advisory GHSA-hxgr-m653-65pw (
"KV store namespace access check ... parent-prefix collision"). H2 and PostgreSQL compare case-sensitively and are unaffected.
The identical collation root cause was fixed for namespace_file_metadata only (#17305/#17310; log keys in #19838).

Details

jdbc-mysql/src/main/resources/migrations/baseline-mysql.sql creates flows, triggers, kv_metadata with
CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; the PRIMARY KEY key and the generated id/namespace columns inherit
the case- and accent-insensitive collation. Lookups WHERE namespace=? AND key=? therefore match across case on MySQL.

2.0.01-schema-mysql.sql switched ONLY namespace_file_metadata key/path/parent_path to utf8mb4_bin (#17305), explicitly
because "Postgres and H2 compare case-sensitively by default and are unaffected". The namespace-bearing identity tables were
not changed.

Kestra namespaces/IDs permit upper case and the application compares them case-sensitively (KVStore.KEY_VALIDATOR_PATTERN,
flow id regex), so the DB and the access model disagree about identity on MySQL only.

Proof of concept

(develop, MySQL 8.4, commit 5046c9a; PostgreSQL control case-sensitive):
Cross-namespace KV (namespaces company.a vs company.A):
PUT /namespaces/company.a/kv/secret = "LOWER" -> 200
PUT /namespaces/company.A/kv/secret = "UPPER" -> 200
GET /namespaces/company.a/kv/secret -> 404 (unreachable after the company.A write)
GET /namespaces/company.A/kv/secret -> "UPPER"
Cross-namespace flow (same id report):
create report@company.a -> 200 ; GET /flows/company.A/report -> returns company.a's flow content
Single-namespace (also reproduced on v2.0.7 and v1.3.44): AlphaKey/alphakey collapse to one row; create report after
Report -> 409; delete one removes the other. PostgreSQL control: all pairs survive independently.
NOT tested: the EE namespace ACL check itself (requires an EE environment / license, which I do not have). In OSS there is no
namespace access control, so only the data-layer conflation is demonstrable here; the ACL bypass is the credible, unverified
consequence.

Impact

Confirmed (any MySQL instance): silent loss/overwrite and cross-namespace conflation of KV entries, flows and trigger state
whose namespace/id differs only by case.

Potential (EE, UNVERIFIED): a user scoped to namespace company.a could read or write company.A's KV (which may hold
secrets), flows and trigger state, because the MySQL layer does not distinguish the two namespaces. This would be a
namespace/tenant isolation bypass (confidentiality + integrity).

Maintainer assessment

Root cause (confirmed). On MySQL, flows, triggers and kv_metadata are created with the case-insensitive collation utf8mb4_unicode_ci in baseline-mysql.sql. Identifiers that differ only by letter case, including the namespace column, therefore resolve to the same row. H2 and PostgreSQL compare case-sensitively and are not affected.

Corrected impact.
- OSS: a correctness bug. Namespaces, flow ids and KV keys that differ only by case collide, overwrite each other or hide each other. OSS has no namespace access control, so there is no security boundary to bypass.
- EE: a namespace isolation bypass is possible but narrow. The EE check compares the requested namespace case-sensitively in Java, and the repository lookup then matches it case-insensitively on MySQL. A user granted company.a can therefore request company.a/<flow id> and get the row stored under company.A. Exploitation requires all of the following:
- MySQL as the backend.
- A victim namespace in the same tenant that differs from the attacker's granted namespace only by letter case.
- A real grant for the attacker on the other casing.

A grant on a parent namespace does not help, because both variants stay inside its subtree. There is no cross-tenant impact.
- Not demonstrated: the EE bypass was reported as unverified. For KV, the evidence shows metadata overwrite and availability impact. A value read is not shown, because values are stored under a namespace-derived path.

Severity. Revised to CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N, score 4.2 (medium), instead of 8.1 (high). The 8.1 rested on the unverified EE bypass.

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:H
BajaAlta
PrivilegiosPR:L
NingunoBajosAltos
InteracciónUI:N
NingunaRequerida
AlcanceS:U
CambiadoSin cambio
ConfidencialidadC:L
AltoBajoNinguno
IntegridadI:L
AltoBajoNinguno
DisponibilidadA:N
AltoBajoNinguno
Score de explotaciónQué tan fácil y probable es que la exploten
5.9/ 10Medio
Vector 5.9 (moderada) · sin evidencia de explotación.
Versiones

Rangos afectados

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

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
mavenio.kestra:kestra
Corregida 2.0.8 -7 d 2.0.10 no afectada
Versiones corregidas2.0.8
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-4cpw-cp2h-qh6q

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