@prisma/studio-core 0.34.1 bundles kysely 0.28.10 (CVE-2026-32763, CVE-2026-33468, CVE-2026-44635)

Abierto
#1,587 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
42/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
javascript, mysql, postgresql, sql, sqlite, typescript

Línea de trabajo

The stale kysely copy comes from the kysely devDependency pin in prisma/studio's package.json, and the bundle is produced by the build that writes dist/metafile-esm.json. Start by checking that pin and the lockfile, then bump it to at least 0.28.17 and rebuild. Done means the metafile lists only kysely >= 0.28.17 and the published-tarball check in the issue passes. This touches release steps and a security fix, so confirm with maintainers before publishing.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

While scanning published npm packages for bundled third-party code we found that @prisma/[email protected] (npm latest) inlines kysely 0.28.10 into dist/ (chunk-W46LCTJX.js and the dist/data/*-core adapters). It comes from the devDependency pin "kysely": "0.28.10" in prisma/studio's package.json. The older @prisma/[email protected] carries the same copy.

  • CVE-2026-32763 (GHSA-wmrf-hv6w-mr66): SQL injection via unsanitized JSON path keys (fixed 0.28.12)
  • CVE-2026-33468 (GHSA-8cpq-38p9-67gx): MySQL SQL injection via insufficient backslash escaping in sql.lit(string) and similar literal paths (fixed 0.28.14)
  • CVE-2026-44635 (GHSA-pv5w-4p9q-p3v2): JSON-path traversal injection via unsanitized path-leg metacharacters in JSONPathBuilder.key()/.at() (fixed 0.28.17)

kysely is not declared as a dependency, so npm audit and SCA tools cannot flag it for you or for Studio users.

We have not assessed exploitability in Studio. Because the copy ships where dependency audits cannot see it, it is easy to miss. We would suggest updating it when convenient, and sooner if untrusted input can reach it in your setup.

Suggested fix: bump the kysely devDependency to >= 0.28.17 and rebuild/publish @prisma/studio-core (and -licensed, if it is still distributed).

Studio distribution

Embedded (@prisma/studio-core as published on npm); this concerns the published package itself, not one setup.

Database

All adapters bundle the same kysely copy; CVE-2026-33468 applies to MySQL / MariaDB, the other two to JSON-path queries.

Prisma & studio-core versions

@prisma/studio-core 0.34.1 (npm latest, 2026-10-15).

Steps to reproduce

Checked against the published tarball on 2026-11-02:

npm pack @prisma/[email protected] && tar xzf prisma-studio-core-0.34.1.tgz
grep -o 'node_modules/.pnpm/kysely@[0-9.]*' package/dist/metafile-esm.json | sort | uniq -c

Output:

1476 node_modules/.pnpm/[email protected]
Expected behavior

The published bundle carries kysely >= 0.28.17.

Actual behavior

Every kysely input in the build metafile is kysely 0.28.10.

Lenguaje dominante
TypeScript
Estrellas
2.2k
Forks
91
Merge medio
15 h 27 min
PR fusionados (30 d)
3

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de prisma/studio

Todos los issues de prisma/studio

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.