CVE-2026-82258

Analyzed Analyzed - Analysis Complete

Race Condition in SvelteKit Query Batch Exposes User Data

Publication date: 2026-08-28

Last updated on: 2026-08-31

Assigner: VulnCheck

Description

SvelteKit versions from 2.38.0 before 2.60.1 contain a race condition in query.batch that allows concurrent requests from different users to merge under a single request context. Attackers can exploit specific timing conditions to access sensitive data from other users' concurrent requests.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-28

Last Modified

2026-08-31

Generated

2026-09-17

AI Q&A

2026-08-28

EPSS Evaluated

2026-09-15

NVD

CVE-2026-82258

EUVD

EUVD-2026-67584

Affected Vendors & Products

Vendor	Product	Version / Range
svelte	sveltekit	From 2.38.0 (inc) to 2.60.1 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-362	The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

Attack-Flow Graph

Executive Summary

This vulnerability is a race condition in SvelteKit versions 2.38.0 to 2.60.1 affecting the query.batch feature. It allows concurrent requests from different users to merge under a single request context. Attackers can exploit specific timing conditions to access sensitive data from other users' concurrent requests.

Detection Guidance

This vulnerability involves a race condition in SvelteKit's query.batch functionality. To detect it, monitor for unusual concurrent request patterns or data leaks between user sessions. Check SvelteKit server logs for overlapping request contexts or unexpected data access. No specific commands are provided in the context.

Impact Analysis

If you use a vulnerable SvelteKit version, attackers could access sensitive data from other users' requests. This could lead to unauthorized data exposure, privacy breaches, or data leaks depending on the application's data handling.

Compliance Impact

This vulnerability could lead to non-compliance with GDPR (data protection) and HIPAA (health data privacy) due to unauthorized data access. Organizations may face legal penalties, fines, or reputational damage if sensitive user data is exposed through this flaw.

Mitigation Strategies

Upgrade SvelteKit to version 2.60.1 or later to address the race condition. Review and restrict access to sensitive data endpoints. Implement rate limiting or request queuing to prevent concurrent request merging. Monitor for suspicious activity or data leaks.

Hi! I’m here to help you understand CVE-2026-82258. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70