Cache poisoning via colliding FileStore filenames
Published Feb 9, 2026 · Updated Feb 9, 2026
Cache poisoning in Litestar before 2.20.0 allows remote attackers to serve cached responses for different URLs through crafted paths. FileStore._safe_file_name() applies Unicode NFKD normalization and concatenates decimal character codes without delimiters, so distinct cache keys resolve to the same filename. Exposure requires response caching with FileStore or other attacker-influenced FileStore keys, and the mixup can disclose cached data or substitute cached content.
Summary
What happened
Cache poisoning in Litestar before 2.20.0 allows remote attackers to serve cached responses for different URLs through crafted paths. FileStore._safe_file_name() applies Unicode NFKD normalization and concatenates decimal character codes without delimiters, so distinct cache keys resolve to the same filename. Exposure requires response caching with FileStore or other attacker-influenced FileStore keys, and the mixup can disclose cached data or substitute cached content.
The record
- CVE
- CVE-2026-25480
- Published
- Feb 9, 2026
- Updated
- Feb 9, 2026
- Vendor
- Litestar
- Product
- Litestar
- Classifications
- CWE-20, CWE-176, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 9, 2026CVE publishedPublication date reported by the CVE source.
- Feb 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.20.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- FileStore key-collision proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo