llamaCVEVulnerability Intelligence
/
Advisory · GitHub · npm · vitest

GHSA-5XRQ-8626-4RWP

When Vitest UI server is listening, arbitrary file can be read and executed

Parche disponible
Descargar PNG JSON
CVSS
—
critical
Fuente: —
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche2 versionesPrimer parche a -81 d de la divulgación
Exposición171 dDesde la divulgación, 1 jun 2026, 9:09 a. m.
Detección168 dDesde la divulgación hasta su ingreso al índice
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Modificada
Explotación
Remediación
Parche 4.1.0
Parche 3.2.6
Monitoreo
Detectada
12 mar 26
1 jun 26
10 sept 26
17 nov 26
20 nov 26
12 mar 26
14 may 26
16 jul 26
17 sept 26
20 nov 26
FechaFaseEventoDetalle
Remediación Parche 4.1.0 vitest · -81 d desde divulgación
Divulgación Publicada GHSA-5XRQ-8626-4RWP divulgada
Remediación Parche 3.2.6 vitest · 0 d desde divulgación
Divulgación Modificada Última actualización del registro
Monitoreo Detectada Ingresó al índice
Resumen
Descripción del advisory
Texto original · GitHub · en inglés

### Summary
Arbitrary file can be read on Windows when Vitest UI server is listening, especially when exposed to the network.

### Impact
Only users that match either of the following conditions are affected:

  • explicitly exposes the Vitest UI server to the network (using `--api.host` or `api.host` config option https://vitest.dev/config/api.html)
  • running the Vitest UI or Browser Mode on Windows

### Details
The API handler for `/__vitest_attachment__` uses the deprecated `isFileServingAllowed` incorrectly.
https://github.com/vitest-dev/vitest/blob/eb1abf08573032a532015b999ad3501c5e89e3bb/packages/ui/node/index.ts#L77
The function expects the passed value to use `cleanUrl` after the check before file system related operation.
Because of this, it is possible to bypass the check by `\\?\\..\\`. This is not possible on Linux as Linux errors if a directory named `?` does not exist.

A similar problem exists in other places as well.
- https://github.com/vitest-dev/vitest/blob/eb1abf08573032a532015b999ad3501c5e89e3bb/packages/vitest/src/api/setup.ts#L103-L105
- https://github.com/vitest-dev/vitest/blob/eb1abf08573032a532015b999ad3501c5e89e3bb/packages/vitest/src/api/setup.ts#L119-L121
- https://github.com/vitest-dev/vitest/blob/eb1abf08573032a532015b999ad3501c5e89e3bb/packages/browser/src/node/commands/fs.ts#L10-L11
- https://github.com/vitest-dev/vitest/blob/eb1abf08573032a532015b999ad3501c5e89e3bb/packages/browser/src/node/plugin.ts#L194-L196
- https://github.com/vitest-dev/vitest/blob/eb1abf08573032a532015b999ad3501c5e89e3bb/packages/browser/src/node/rpc.ts#L115-L121

That said, this `isFileServingAllowed` check does not actually prevent the API to be abused. Since the API has rerun feature and file write feature, it's possible to run arbitrary script by writing a script as a test file using `saveTestFile` and running it using `rerun`. This means exposing the API / Vitest UI is equivalent to giving script execution access.
On the browser mode side, there're `readFile` / `writeFile` / `saveSnapshotFile`. So exposing the browser mode is equivalent to giving file read / write access.

### PoC
1. Run Vitest UI
2. Get the API token by `curl http://localhost:51204/__vitest__/`
3. Run `curl "http://localhost:51204/__vitest_attachment__?path=C:\\path\\to\\project\\?\\..\\..\\secret.txt&contentType=text/plain&token=$TOKEN"` (TOKEN is the API token)
4. curl shows the content of `secret.txt` that is outside the project directory

Mitigations

Vitest now ships two configuration flags, `allowWrite` https://vitest.dev/config/api.html#api-allowwrite and `allowExec` https://vitest.dev/config/api.html#api-allowexec, that gate the privileged operations exploited by this vulnerability. Both are disabled by default whenever the API server is bound to a non-`localhost` host, ensuring that exposing the server to the network no longer implicitly grants write or execute capabilities to remote clients.

When these flags are disabled, the UI also enters a read-only mode: in-browser code editing and test file execution are turned off, removing the attack surface that allowed remote code execution. Many Browser Mode features are also disabled, like attachments, artifacts or snapshots. See `browser.api` https://vitest.dev/config/browser/api.html#api-allowwrite.

Users who require the full interactive UI on a networked host must explicitly opt in by setting `allowWrite` and/or `allowExec` to `true`.

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

Versiones

Rangos afectados

Afectada Corregida Última
vitest< 3.2.6
vitest≥ 4.0.0 < 4.1.0
3.2.6
4.0.0
4.1.0
5.1.0
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
npmvitest
Corregida 3.2.6, 4.1.0 0 d · -81 d 5.1.0 no afectada
Versiones corregidas3.2.64.1.0
Explotación

Arsenal público

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

Referencias
Advisoryhttps://nvd.nist.gov/vuln/detail/CVE-2026-47429
Otrahttps://github.com/vitest-dev/vitest/security/advisories/GHSA-5xrq-8626-4rwp
Otrahttps://github.com/vitest-dev/vitest/pull/10445
Otrahttps://github.com/vitest-dev/vitest/pull/9350
Otrahttps://github.com/vitest-dev/vitest/commit/20e00ef7808de6d330c5e2fda530f686e08f1c8d
Otrahttps://github.com/vitest-dev/vitest/commit/af88b1f5d82844a4761ea9a977156c98e2b14ca8
Otrahttps://github.com/vitest-dev/vitest
Otrahttps://github.com/vitest-dev/vitest/blob/eb1abf08573032a532015b999ad3501c5e89e3bb/packages/browser/src/node/commands/fs.ts#L10-L11
Otrahttps://github.com/vitest-dev/vitest/blob/eb1abf08573032a532015b999ad3501c5e89e3bb/packages/browser/src/node/plugin.ts#L194-L196
Otrahttps://github.com/vitest-dev/vitest/blob/eb1abf08573032a532015b999ad3501c5e89e3bb/packages/browser/src/node/rpc.ts#L115-L121
Otrahttps://github.com/vitest-dev/vitest/blob/eb1abf08573032a532015b999ad3501c5e89e3bb/packages/ui/node/index.ts#L77
Otrahttps://github.com/vitest-dev/vitest/blob/eb1abf08573032a532015b999ad3501c5e89e3bb/packages/vitest/src/api/setup.ts#L103-L105
Ver 3 referencias más
Otrahttps://github.com/vitest-dev/vitest/blob/eb1abf08573032a532015b999ad3501c5e89e3bb/packages/vitest/src/api/setup.ts#L119-L121
Otrahttps://github.com/vitest-dev/vitest/releases/tag/v3.2.5
Otrahttps://github.com/vitest-dev/vitest/releases/tag/v4.1.0

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