CVE-2026-114061
Awaiting Analysis Awaiting Analysis - Queue

Cross-Site Scripting in SvelteKit Prerendered Pages

Vulnerability report for CVE-2026-114061, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-21

Last updated on: 2026-10-28

Assigner: VulnCheck

Description

SvelteKit (@sveltejs/kit) before 3.0.0 contains a cross-site scripting vulnerability in prerendered pages because a cache-control header value set via setHeaders is inserted without escaping into a <meta http-equiv="cache-control"> tag. An attacker who can influence that untrusted value at prerender time can break out of the content attribute and inject HTML or JavaScript that executes when users visit the page.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-21
Last Modified
2026-10-28
Generated
2026-11-10
AI Q&A
2026-10-21
EPSS Evaluated
2026-11-08
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
sveltejs kit 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a cross-site scripting (XSS) flaw in SvelteKit versions before 3.0.0. It occurs in prerendered pages when the cache-control header value, set via setHeaders from an untrusted source, is inserted without escaping into a meta tag. Attackers can inject malicious HTML or JavaScript by manipulating this value during prerendering, which executes when users visit the page.

Detection Guidance

To detect this vulnerability, check if your SvelteKit application uses versions before 3.0.0 and prerenders pages with setHeaders for cache-control. Inspect the HTML output of prerendered pages for unescaped cache-control meta tags. Use commands like grep to search for setHeaders usage in your codebase.

Impact Analysis

An attacker could exploit this to inject and execute malicious scripts in the context of a user's browser session. This could lead to theft of session cookies, sensitive data exposure, or unauthorized actions performed on behalf of the user. The impact depends on the privileges of the affected user and the nature of the injected payload.

Compliance Impact

This XSS vulnerability could lead to unauthorized data access or modification, violating GDPR's integrity and confidentiality principles or HIPAA's safeguards for protected health information. Organizations may face compliance violations if user data is compromised due to this flaw.

Mitigation Strategies

Upgrade SvelteKit to version 3.0.0 or later. If upgrading is not immediately possible, avoid using setHeaders to forward untrusted cache-control header values on prerendered pages. Use a fixed, trusted cache policy instead.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-114061. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...