CVE
kit cross-site scripting in server-side route resolution
- Exploited
- No known exploitation
- Fix
- Fixed in 2.70.4, 3.1.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.70.4, 3.1.1.
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 12/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
SvelteKit, a web application framework, is affected when apps use server-side route resolution. A remote attacker who gets a user to open a crafted link can make the user's browser run JavaScript from another origin, which could expose data the user can access, and the attack needs no login but does require the user to click the link.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
SvelteKit is a framework for rapidly developing robust, performant web applications using Svelte. Prior to versions 2.70.4 and 3.1.1, apps configured with router.resolution: 'server' could treat a pathname beginning with // as a protocol-relative module specifier during client-side navigation. A socially engineered link could therefore make server-side route resolution import and execute JavaScript from another origin in the user's browser. This issue is fixed in 2.70.4 and 3.1.1.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 2.70.4, 3.1.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-128116 (SvelteKit: Protocol-relative module import during server-side route resolution allows cross-origin script execution), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-128116 (entry last updated 2026-11-13):
Affected:
- sveltejs kit: fixed in 2.70.4; from 3.0.0, fixed in 3.1.1
Fixed versions: 2.70.4, 3.1.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-128116 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128116 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/sveltejs/kit/security/advisories/GHSA-rqp5-r3wg-vg35
- https://github.com/sveltejs/kit/pull/17620
- https://github.com/sveltejs/kit/commit/0a2e58cbccdd46cac20aa5af4e2edf17e0da11dd
- https://github.com/sveltejs/kit/commit/a8f7c1e09f13524d3b71d814bad9c15c9f33ef49
- https://github.com/sveltejs/kit/releases/tag/@sveltejs/kit@2.70.4
- https://github.com/sveltejs/kit/releases/tag/@sveltejs/kit@3.1.1
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-128116
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-128116"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- sveltejs kit
fixed in 2.70.4; From 3.0.0 · fixed in 3.1.1
Evidence 7
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
Other links · 5
- Repository
- Repository
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-128116
Is CVE-2026-128116 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-128116?
kit: before 2.70.4; from 3.0.0 before 3.1.1.Source: cve.now feed data
How do I fix CVE-2026-128116?
Upgrade to a fixed version: 2.70.4, 3.1.1.Source: cve.now feed data