# CVE-2026-128119: SvelteKit: Private `query.batch` functions could collide, producing unexpected parameter / function combinations


- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 13 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** DHI-i4qf-luqi-aafz-t2j4, GHSA-6cf5-gc4q-fm3x

## What is CVE-2026-128119?

CVE-2026-128119 is a medium-severity vulnerability in sveltejs kit, published on 13 Nov 2026. 

### Official description

SvelteKit is a framework for rapidly developing robust, performant web applications using Svelte. From version 2.60.1 until 3.1.1, applications using the experimental remote functions flag could assign the same generated identifier to separate non-exported query.batch functions. When those private functions shared a request batch, arguments intended for one function could be passed to another function, causing unexpected cross-function processing and possible disclosure of function arguments. This issue is fixed in 3.1.1.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-128119?

1 open source package ship an affected version, including @sveltejs/kit.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `@sveltejs/kit` | npm | `pkg:npm/%40sveltejs/kit` | From 2.60.1 | 3.1.1 |

Status by vendor (upstream, then each distribution release and vendor build):

| Who | Release | Status | Packages | Fixed in |
| --- | --- | --- | --- | --- |
| Upstream |  | fixed | `@sveltejs/kit` | 3.1.1 |

## How do I fix CVE-2026-128119?

Upgrade @sveltejs/kit to 3.1.1 or later.

## Is CVE-2026-128119 being exploited?

There is no known exploitation of CVE-2026-128119 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-128119 and fix it if it is affected.

What it is: CVE-2026-128119 is a medium-severity vulnerability in sveltejs kit, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-128119 in the wild and no public exploit code.

Affected packages and fixed versions:
- @sveltejs/kit (npm): affected from 2.60.1; fixed in 3.1.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-128119/ (Markdown: https://insights.sbomify.com/CVE-2026-128119/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-128119
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-128119
- OSV: https://osv.dev/vulnerability/CVE-2026-128119

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-128119/
Summaries are generated and may contain mistakes; the official description above is the record.
