Résumé
esbuild's development server (versions 0.27.3 up to but not including 0.28.1) allows arbitrary file read on Windows: a crafted request path can escape the served directory and read files elsewhere on disk. It affects the development server only, not production builds, but anyone running `esbuild --serve` on Windows is exposed to any local or networked attacker who can reach the server.
Comment le corriger
- Upgrade `esbuild` to 0.28.1 or later, which fixes the dev-server path handling.
- Until you upgrade, do not expose the esbuild dev server beyond localhost, and run it only behind a trusted network boundary.
Comment l’éviter dans votre code
- Never expose development servers to untrusted networks; bind them to localhost and put them behind a VPN or firewall if remote access is genuinely needed.
- Keep build tooling updated; dev-server file-serving bugs are common and only matter while the server is reachable.
- Treat the development server as untrusted infrastructure, kept separate from anything that holds secrets.
Références
Vulnérabilités liées
Tout Supply chain →- MEDIUMCVE-2026-61431
PraisonAI: ContextGatherer include resolution permits absolute and traversal reads outside the workspace
- MEDIUMCVE-2026-60088
PraisonAI: Project custom command templates can read outside-workspace files into model prompts
- MEDIUMCVE-2026-61432
PraisonAI: FastContext path resolution permits absolute and traversal reads outside the workspace
- HIGHGHSA-5rmq-chc7-m22f
Vibe-Trading file-read tools expose arbitrary server-readable files
- HIGHCVE-2026-77246
MCP Atlassian: MCP HTTP Client Server-Local File Exfiltration via Unvalidated Attachment Upload Path
- HIGHCVE-2026-75859
CodeWhale: Project config `instructions` override enables arbitrary file read into AI system prompt via cloned repository