CVE-2026-25480
Undergoing Analysis Undergoing Analysis - In Progress
Cache Poisoning in Litestar FileStore via Key Collision

Publication date: 2026-02-09

Last updated on: 2026-02-17

Assigner: GitHub, Inc.

Description
Litestar is an Asynchronous Server Gateway Interface (ASGI) framework. Prior to 2.20.0, FileStore maps cache keys to filenames using Unicode NFKD normalization and ord() substitution without separators, creating key collisions. When FileStore is used as response-cache backend, an unauthenticated remote attacker can trigger cache key collisions via crafted paths, causing one URL to serve cached responses of another (cache poisoning/mixup). This vulnerability is fixed in 2.20.0.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-09
Last Modified
2026-02-17
Generated
2026-06-16
AI Q&A
2026-02-09
EPSS Evaluated
2026-06-15
NVD
CVE-2026-25480
EUVD
EUVD-2026-6498
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
litestar litestar to 2.20.0 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-176 The product does not properly handle when an input contains Unicode encoding.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability exists in the Litestar ASGI framework prior to version 2.20.0. The issue arises because the FileStore component maps cache keys to filenames using Unicode NFKD normalization and ord() substitution without separators, which can cause different cache keys to collide.

When FileStore is used as a response-cache backend, an unauthenticated remote attacker can exploit this by crafting specific paths that cause cache key collisions. This results in one URL serving the cached response intended for another URL, effectively causing cache poisoning or mixup.

The vulnerability is fixed in Litestar version 2.20.0.

Impact Analysis

This vulnerability can impact you by allowing an unauthenticated remote attacker to cause cache poisoning or mixup. This means that users may receive incorrect or unintended cached responses for certain URLs.

Such behavior can lead to information disclosure, as sensitive data intended for one user or endpoint might be served to another. It can also undermine the integrity and reliability of the application responses.

Compliance Impact

I don't know

Detection Guidance

I don't know

Mitigation Strategies

To mitigate this vulnerability, you should upgrade Litestar to version 2.20.0 or later, where the issue with FileStore cache key collisions has been fixed.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-25480. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart