CVE-2026-25480

FileStore key canonicalization collisions allow response cache mixup/poisoning (ASCII ord + Unicode NFKD)

Published Feb 9, 2026 CVSS 3.1 · 6.5 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability in Litestar arises from how its FileStore component creates cache keys. It normalizes request paths using Unicode NFKD and substitutes character code points via ord() without separating delimiters, which can produce identical keys for different URLs. An attacker who can send arbitrary HTTP requests to the server can craft paths that collide with legitimate cache keys, resulting in one URL serving the cached response of another. The effect is that sensitive data may be disclosed or the application may provide incorrect content, meeting CWE-176. The impact is not complete control over the system but can lead to information disclosure and functional disruption.

Affected Systems

Litestar, an ASGI framework produced and maintained by litestar-org, is vulnerable in all releases prior to version 2.20.0. The problem is specific to deployments that use the FileStore as a response‑cache backend; if that feature is not enabled, the risk is mitigated.

Risk and Exploitability

The CVSS score of 6.5 indicates moderate severity. The EPSS score is below 1 %, implying a very low probability of exploitation in the wild, and the vulnerability is not currently listed in the CISA KEV catalog. Nevertheless, an unauthenticated attacker can reach the server over HTTP and send a crafted path to trigger the collision. The attack requires no special privileges, depends on the presence of the FileStore response‑cache backend, and leads directly to cache poisoning. While the likelihood of exploitation is low, the potential information disclosure is significant enough to warrant patching.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Litestar to version 2.20.0 or later
  • Disable the FileStore response‑cache backend on all publicly exposed services until the upgrade can be applied
  • Verify that cached responses are served from a backend that uses a deterministic key scheme and reconfigure or patch any custom caching logic that reproduces the colliding behaviour

Generated by OpenCVE AI on April 18, 2026 at 18:14 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-vxqx-rh46-q2pg Litestar's FileStore key canonicalization collisions allow response cache mixup/poisoning (ASCII ord + Unicode NFKD)
History
Type Values Removed Values Added
First Time appeared Litestar
Litestar litestar
CPEs cpe:2.3:a:litestar:litestar:*:*:*:*:*:*:*:*
Vendors & Products Litestar
Litestar litestar
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Litestar-org
Litestar-org litestar
Vendors & Products Litestar-org
Litestar-org litestar
Type Values Removed Values Added
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.
Title FileStore key canonicalization collisions allow response cache mixup/poisoning (ASCII ord + Unicode NFKD)
Weaknesses CWE-176
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N'}

Weaknesses
  • CWE-176

    Improper Handling of Unicode Encoding

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Feb 10, 2026, 4:01 PM
Reserved
Feb 2, 2026, 4:31 PM
Status
Analyzed
Published
Feb 9, 2026, 8:15 PM
Modified
Jun 17, 2026, 10:24 AM