Live › vulnerability › CVE-2026-114061
Go to dashboardSvelteKit prerendered pages put a cache-control header value into a meta tag without escaping it when the app sets that header from untrusted input via setHeaders. An attacker who controls that value at prerender time can inject HTML or JavaScript that runs for visitors of the generated page.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 20:45 UTC, 1h before NVD. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| @sveltejs/kit | npm | < 3.0.0 | 3.0.0 |
Search the app for setHeaders calls that set cache-control from request data, query params, or other untrusted sources on pages that are prerendered.
3.0.0 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
Applications that prerender pages and use setHeaders to set a cache-control header from an untrusted source are vulnerable to cross-site scripting (XSS).
SvelteKit inserts the header value into a <meta http-equiv="cache-control"> tag without escaping it. An attacker who can influence this value at prerender time can break out of the content attribute and inject HTML or JavaScript into the generated page. The injected code can then execute when users visit the page.
The fix escapes the header value before inserting it into the generated HTML. Upgrade to @sveltejs/kit version 3.0.0 or later.
Avoid forwarding untrusted cache-control header values with setHeaders on prerendered pages. Use a fixed, trusted cache policy instead.
This page as .md · .json · in your agent: get_signal("CVE-2026-114061")
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.