CVE-2026-114062: SvelteKit server-side request forgery in self-fetch fallbacks

CVE-2026-114062 · Severity: medium · CVSS 5.3 · Published 2026-10-21

SvelteKit is a web application framework that handles server-side rendering and request processing. A vulnerability allows remote attackers to manipulate the origin of server-side fallback requests by spoofing HTTP headers, which are then followed through automatic redirects to reach internal services. This could lead to data exposure from systems that should be inaccessible from the internet.

Technologies: SvelteKit. Vendors: Svelte.

Quick answers

Is CVE-2026-114062 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-114062 being exploited in the wild.
How severe is CVE-2026-114062?
Medium severity, with a CVSS score of 5.3, published 21 October 2026.
Which products and versions are affected?
SvelteKit before 3.0.0.
Is there a fix for CVE-2026-114062?
Yes: fixed in 3.0.0. Until then: Configure a trusted fixed request origin where supported; for adapter-node, set the paths.origin configuration to the application's trusted origin. Alternatively, use a trusted reverse proxy that validates allowed request hosts and supplies trusted host/protocol metadata, ensuring forwarded headers are not accepted directly from untrusted clients. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-114062 attacked?
It is attacked over the network.
Am I affected by CVE-2026-114062?
Check whether you run SvelteKit at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Fixed in: 3.0.0

Configure a trusted fixed request origin where supported; for adapter-node, set the paths.origin configuration to the application's trusted origin. Alternatively, use a trusted reverse proxy that validates allowed request hosts and supplies trusted host/protocol metadata, ensuring forwarded headers are not accepted directly from untrusted clients.

Technical details

A server-side request forgery (SSRF) vulnerability exists in SvelteKit's self-fetch fallback mechanism, which makes server-side requests to URLs derived from the incoming request origin. An attacker can manipulate the Host or forwarded headers to redirect these requests to an attacker-controlled server, which then performs a redirect to internal services. The vulnerability requires influence over the request origin and the ability to trigger one of the fallback paths; the fix in version 3.0.0 disables automatic redirect following for these fallback requests.

Affected products

  • Svelte SvelteKit before 3.0.0

Timeline

  • 2026-10-05: disclosed
  • 2026-10-20: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.