# What is Dev Server Exposure?

> Dev server exposure is making a development server reachable beyond your machine, through a network binding or a public tunnel.

Source: https://layerv.ai/glossary/dev-server-exposure/

---

[← All Terms](https://layerv.ai/glossary/) 

# What is Dev Server Exposure?

Development servers such as Vite, webpack-dev-server, and framework dev modes are built for one trusted user on localhost. Flags like --host bind them to every network interface, and a public tunnel puts them on the internet.

They are not hardened for hostile traffic. CISA lists a Vite vulnerability among known exploited vulnerabilities and notes that only dev servers exposed to the network are affected.

## How LayerV Implements This

Keep the dev server on localhost and publish it with the qURL CLI. Recipients reach it through their own link, and by protocol design, requests without a session get no response.

## Related

[Localhost Tunnel](https://layerv.ai/glossary/localhost-tunnel/) [Attack Surface Reduction](https://layerv.ai/glossary/attack-surface-reduction/)

[Fix Vite “Blocked request. This host is not allowed” →](https://layerv.ai/guides/fix-vite-blocked-request-host-not-allowed/) [Guide: Share a dev server with a client →](https://layerv.ai/guides/share-dev-server-with-client/) [Research: Developer and AI tools in CISA KEV →](https://layerv.ai/research/dev-tool-kev/)



---

*This markdown version is auto-generated from [https://layerv.ai/glossary/dev-server-exposure/](https://layerv.ai/glossary/dev-server-exposure/) for AI agents. Curated agent resources: [llms.txt](https://layerv.ai/llms.txt). For the full interactive experience, visit the HTML version.*