Only the latest published 0.x release receives fixes. Pre-1.0 releases are supported on a best-effort basis.
Report privately through GitHub's private vulnerability reporting on this repository. Do not open a public issue for a security problem.
Include the version, a minimal reproduction, and the impact you believe it has. You will get an acknowledgement, and a fix or an explanation of why the report is out of scope.
- Output directory escape or arbitrary file write through a crafted route or link
- Injection into generated HTML through captured state, stylesheet content, or route data
- Command execution beyond the explicit
serveCmdoption - Leakage of
storageStatecontents, cookies, or page data into logs or output - Supply chain issues in published dependencies
- The prerenderer executing your app's own client code by design. Prerendering runs your bundle in a real browser; treat it with the same trust as running your app.
- Project configuration executing as code.
snappy.config.jsis imported as a module andserveCmdruns a shell command, exactly likevite.config.jsand npm scripts. Both are trusted input. - Anything reachable on the loopback build server. During a run it serves the output directory — including any API responses captured into generated HTML — on an ephemeral
127.0.0.1port, so a local process can read it. - Third-party scripts your app loads. They are allowed by default so CMS-backed apps render with data; set
blockThirdParty: true(optionally withallowedHosts) to stop them executing during a build. - Integrity of the optional Chrome for Testing download beyond HTTPS, unless
browserDownloadHashis set. The archive is fetched over TLS from Google's version-pinned bucket, and Chrome for Testing publishes no checksum feed to verify against. SetbrowserDownload: falseif that trust model is not acceptable in your environment.
blockThirdParty: truewithallowedHoststo keep only the origins the build actually needs, so analytics and widgets never run during a build.browserDownload: false(orbrowserDownloadHash) to control the fallback browser download.blockThirdParty: trueby default, so third-party scripts do not execute during rendering;allowedHostsnarrows it further rather than disabling it.storageStatefiles are read but never logged or written into the output; keep them out of the repository.- Generated HTML escapes captured state keys and values against script breakout.