{"answers":{"affected":"3 open source packages ship an affected version, including litestar.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48061 exists.","fix":"Upgrade litestar to 2.22.0 or later.","what":"CVE-2026-48061 is a medium-severity vulnerability in litestar-org litestar, published on 3 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-48061 and fix it if it is affected.\n\nWhat it is: CVE-2026-48061 is a medium-severity vulnerability in litestar-org litestar, published on 3 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48061 exists.\n\nAffected packages and fixed versions:\n- litestar (PyPI): affected all versions; fixed in 2.22.0\n- litestar (PyPI): affected all versions; fixed in 2.22.0\n- litestar (PyPI): affected all versions; fixed in 2.22.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-48061/ (Markdown: https://insights.sbomify.com/CVE-2026-48061/index.md)","id":"CVE-2026-48061","markdown":"https://insights.sbomify.com/CVE-2026-48061/index.md","name":"CVE-2026-48061","record":{"aliases":["GHSA-3qmc-cj7q-62hv","PYSEC-2026-2603"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass","other"],"network_reachable":"yes","non_default_config":true,"product_category":"Python ASGI framework","requires_auth":"none","summary":"Attackers can bypass host validation in Litestar by spoofing the X-Forwarded-Host header, enabling password reset poisoning and cache poisoning attacks.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-644","name":"Improper Neutralization of HTTP Headers for Scripting Syntax"}],"description":"Litestar is an Asynchronous Server Gateway Interface (ASGI) framework. In versions prior to 2.22.0, 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. The 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, this enables host header injection attacks such as password reset poisoning, cache poisoning, and server-side request routing manipulation. Any application using AllowedHostsConfig is affected when deployed without a reverse proxy that strips X-Forwarded-Host, or when accepting HTTP/1.0 connections. This issue has been fixed in version 2.22.0.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Litestar: AllowedHostsMiddleware bypasses host validation via client-controlled X-Forwarded-Host header","id":"CVE-2026-48061","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"CodeIgniter: Uploaded file extension validation bypass in `ext_in` rule","id":"CVE-2026-48062"},"packages":[{"ecosystem":"PyPI","fixed":["2.22.0"],"introduced":["0"],"last_affected":[],"package":"litestar","purl":null,"source":"GHSA-3qmc-cj7q-62hv"},{"ecosystem":"PyPI","fixed":["2.22.0"],"introduced":["0"],"last_affected":[],"package":"litestar","purl":"pkg:pypi/litestar","source":"GHSA-3qmc-cj7q-62hv"},{"ecosystem":"PyPI","fixed":["2.22.0"],"introduced":["0"],"last_affected":[],"package":"litestar","purl":"pkg:pypi/litestar","source":"PYSEC-2026-2603"}],"prev":{"headline":"Litestar: HTML Injection Through CSRF Token","id":"CVE-2026-48060"},"products":["litestar"],"published":"2026-08-03","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-04","vendors":["litestar-org"]},"summary":"Attackers can bypass host validation in Litestar by spoofing the X-Forwarded-Host header, enabling password reset poisoning and cache poisoning attacks.","url":"https://insights.sbomify.com/CVE-2026-48061/"}