Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-2p2x-hpg8-cqp2 | Litestar's CORS origin allowlist has a bypass due to unescaped regex metacharacters in allowed origins |
Tue, 17 Feb 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Litestar
Litestar litestar |
|
| CPEs | cpe:2.3:a:litestar:litestar:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Litestar
Litestar litestar |
Tue, 10 Feb 2026 17:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 10 Feb 2026 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Litestar-org
Litestar-org litestar |
|
| Vendors & Products |
Litestar-org
Litestar-org litestar |
Mon, 09 Feb 2026 19:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Litestar is an Asynchronous Server Gateway Interface (ASGI) framework. Prior to 2.20.0, CORSConfig.allowed_origins_regex is constructed using a regex built from configured allowlist values and used with fullmatch() for validation. Because metacharacters are not escaped, a malicious origin can match unexpectedly. The check relies on allowed_origins_regex.fullmatch(origin). This vulnerability is fixed in 2.20.0. | |
| Title | Litestar has a CORS origin allowlist bypass due to unescaped regex metacharacters in allowed origins | |
| Weaknesses | CWE-942 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-02-10T16:01:16.807Z
Reserved: 2026-02-02T16:31:35.820Z
Link: CVE-2026-25478
Updated: 2026-02-10T15:30:26.193Z
Status : Analyzed
Published: 2026-02-09T20:15:57.017
Modified: 2026-02-17T15:15:29.523
Link: CVE-2026-25478
No data.
OpenCVE Enrichment
Updated: 2026-04-18T18:15:06Z
Github GHSA