Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-27118: CWE-346: Origin Validation Error in sveltejs kit

0
Medium
VulnerabilityCVE-2026-27118cvecve-2026-27118cwe-346
Published: Fri Feb 20 2026 (02/20/2026, 21:24:55 UTC)
Source: CVE Database V5
Vendor/Project: sveltejs
Product: kit

Description

SvelteKit is a framework for rapidly developing robust, performant web applications using Svelte. Versions of @sveltejs/adapter-vercel prior to 6.3.2 are vulnerable to cache poisoning. An internal query parameter intended for Incremental Static Regeneration (ISR) is accessible on all routes, allowing an attacker to cause sensitive user-specific responses to be cached and served to other users. Successful exploitation requires a victim to visit an attacker-controlled link while authenticated. Existing deployments are protected by Vercel's WAF, but users should upgrade as soon as possible. This vulnerability is fixed in 6.3.2.

AI-Powered Analysis

AILast updated: 02/20/2026, 21:47:04 UTC

Technical Analysis

CVE-2026-27118 is a vulnerability classified under CWE-346 (Origin Validation Error) affecting the @sveltejs/adapter-vercel package used in the SvelteKit framework for building web applications. The flaw arises because an internal query parameter intended for Incremental Static Regeneration (ISR) is exposed and accessible on all routes, regardless of user or route context. This parameter controls caching behavior, and its exposure allows an attacker to craft URLs that cause sensitive, user-specific responses to be cached improperly. When a victim, who is authenticated, visits such a maliciously crafted link, the server caches the personalized response. Subsequent requests by other users may then receive this cached sensitive data, leading to information disclosure. The vulnerability does not require the attacker to have privileges or authentication but does require the victim's interaction with the malicious link. Vercel’s WAF offers some mitigation by filtering suspicious requests, but it is not a complete fix. The issue was addressed in version 6.3.2 of the adapter by properly restricting access to the internal query parameter and improving origin validation to prevent cache poisoning. The CVSS 4.0 score is 5.3 (medium), reflecting network attack vector, low complexity, no privileges required, but requiring user interaction and resulting in limited confidentiality impact. No known exploits have been reported in the wild as of now.

Potential Impact

The primary impact of this vulnerability is the potential leakage of sensitive user-specific data due to cache poisoning. Organizations using vulnerable versions of @sveltejs/adapter-vercel on Vercel may inadvertently serve cached responses containing private information to unauthorized users. This can lead to breaches of confidentiality, loss of user trust, and potential regulatory compliance violations, especially in sectors handling sensitive personal or financial data. Since the vulnerability requires user interaction, phishing or social engineering attacks could be leveraged to exploit it. The scope includes any web application built with SvelteKit using the vulnerable adapter version and deployed on Vercel, which is a popular hosting platform. While availability and integrity impacts are minimal, the confidentiality breach risk is significant for affected deployments. The presence of Vercel’s WAF reduces the likelihood of exploitation but does not eliminate it, making timely patching critical. Organizations with high-value or sensitive user data are at greater risk, and failure to remediate could result in reputational damage and legal consequences.

Mitigation Recommendations

1. Upgrade the @sveltejs/adapter-vercel package to version 6.3.2 or later immediately to apply the fix that restricts access to the internal ISR query parameter and prevents cache poisoning. 2. Review and audit caching configurations in SvelteKit applications to ensure no sensitive data is cached improperly, especially when using ISR or similar mechanisms. 3. Implement strict validation and sanitization of query parameters to prevent unauthorized manipulation of cache keys. 4. Employ Content Security Policy (CSP) and other HTTP security headers to reduce the risk of phishing and social engineering attacks that could trick users into clicking malicious links. 5. Monitor application logs and cache behavior for anomalies indicating potential cache poisoning attempts. 6. If using Vercel, verify that the WAF is enabled and configured correctly, but do not rely solely on it as a mitigation. 7. Educate users about the risks of clicking unknown or suspicious links, especially when authenticated. 8. Consider implementing additional application-layer controls to segregate cached content by user identity or session where feasible.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-02-17T18:42:27.043Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6998d2dfbe58cf853bb9b978

Added to database: 2/20/2026, 9:32:15 PM

Last enriched: 2/20/2026, 9:47:04 PM

Last updated: 2/21/2026, 12:18:17 AM

Views: 5

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats