In affected projects, a server-only import through src/params.js could enter a client bundle and potentially expose server secrets.The SvelteKit advisory rates the flaw High. The reported consequence is possible disclosure of statically replaced private environment values or other server secrets, rather than code execution.
What it allows
How Does CVE-2026-128118 Reach a Client Bundle?
SvelteKit normally prevents server-only modules from entering browser code. The NVD record says the build-time guard missed src/params.js as a client entry point, even though parameter matchers can run in a browser.
A server-only module imported along that path could therefore reach the generated client bundle. The record says statically replaced private environment values or other server secrets could be exposed; exposure depends on the project's imports and built output.
This is a confidentiality issue, and the advisory's CVSS 3.1 vector assigns high confidentiality impact. It assigns no integrity or availability impact. For prioritization, see Brandefense's Vulnerability Intelligence platform product page.
What Is Known About Exploitation?
CVE-2026-128118 was absent from CISA's KEV catalog version 2026.11.13, checked November 16. That dated catalog fact does not determine whether an individual deployment exposed secrets. Treat real-world exploitation status as unknown.
Who is affected
Version Check
| Release Line | Affected Range | Fixed In |
|---|---|---|
| 3.x | 3.0.0 to before 3.1.1 | 3.1.1 |
For distribution packages and custom builds, check the supplier’s advisory.
The version interval identifies affected package releases. Potential secret disclosure also requires a server-only import through src/params.js and a built client bundle containing a sensitive value.
Which SvelteKit Projects Are Affected by CVE-2026-128118?
The SvelteKit advisory lists @sveltejs/kit versions 3.0.0 through 3.1.0, inclusive, as affected. Version 3.1.1 is patched. The potential disclosure path requires server-only imports through src/params.js.
Check the resolved SvelteKit package version in the project lockfile and the version used to build each deployed artifact. Then review imports through the parameter matcher module and inspect the generated client assets for sensitive values using an approved internal process.
Upgrade affected projects to 3.1.1 or a later supported release, then rebuild and redeploy client assets. Verify that the rebuilt artifact uses the fixed package and that sensitive values are absent. If a secret was present in a published bundle, follow your incident process to rotate it and assess access.
The Vulnerability Management 101 guide provides a general verification workflow. The vulnerability intelligence glossary explains how evidence informs patch priority.
Timeline
-
2026-10-29
The SvelteKit advisory was published, and the project released @sveltejs/kit 3.1.1 with the server-only import fix.
-
2026-11-13
NVD published its CVE record describing the client-entry-point guard failure.
-
2026-11-16
The GitHub advisory was updated. Brandefense reviewed the advisory and the CISA KEV catalog snapshot.
What to do
-
Inventory builds and imports
Identify projects built with @sveltejs/kit 3.0.0 through 3.1.0. Review server-only imports through src/params.js and the client assets produced by those builds.
-
Upgrade and rebuild
Upgrade @sveltejs/kit to 3.1.1 or a later supported release. Rebuild and redeploy affected client assets rather than relying on a package update alone.
-
Verify the running artifact
Confirm the deployed build used @sveltejs/kit 3.1.1 or later. Check that server-only imports are rejected from browser code and sensitive values are absent from distributed assets.
-
Respond to confirmed exposure
If a secret was present in a published client bundle, rotate it and assess access through your incident process. Preserve findings without placing sensitive values in public tickets.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-128118 in Brandefense Atlas
The Atlas record of CVE-2026-128118: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
Which SvelteKit versions does CVE-2026-128118 affect?
The SvelteKit advisory lists @sveltejs/kit 3.0.0 through 3.1.0, inclusive. Version 3.1.1 contains the fix.
Does every project on an affected version leak secrets?
The reported path requires a server-only import through src/params.js. Inspect the project's imports and generated client assets to determine whether sensitive values were included.
Is CVE-2026-128118 known to be exploited?
Real-world exploitation status is unknown. The CVE was absent from CISA KEV catalog version 2026.11.13; this dated catalog fact does not establish exploitation.
What should teams verify after upgrading?
Confirm the deployed build used @sveltejs/kit 3.1.1 or later. Reinspect client assets for sensitive values and rotate any secret found in a published bundle.
Sources
- SvelteKit server-only module import guard advisorySvelteKit
- @sveltejs/kit 3.1.1 releaseSvelteKit
- NVD record for CVE-2026-128118NIST National Vulnerability Database
- Known Exploited Vulnerabilities CatalogCISA