{"answers":{"affected":"3 open source packages ship an affected version, including litestar. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-25479 in the wild and no public exploit code.","fix":"Upgrade litestar to 2.20.0 or later.","what":"CVE-2026-25479 is a medium-severity vulnerability in litestar-org litestar, published on 9 Feb 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-25479 and fix it if it is affected.\n\nWhat it is: CVE-2026-25479 is a medium-severity vulnerability in litestar-org litestar, published on 9 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-25479 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- litestar (PyPI): affected all versions; fixed in 2.20.0\n- litestar (PyPI): affected from 2.19.0; fixed in 2.20.0\n- litestar (PyPI): affected from 2.19.0; fixed in 2.20.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-25479/ (Markdown: https://insights.sbomify.com/CVE-2026-25479/index.md)","id":"CVE-2026-25479","markdown":"https://insights.sbomify.com/CVE-2026-25479/index.md","name":"CVE-2026-25479","record":{"aliases":["GHSA-93ph-p7v4-hwh4","PYSEC-2026-2196"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Python ASGI framework","requires_auth":"none","summary":"Attackers can bypass host validation in Litestar by exploiting unescaped regex metacharacters in allowlist patterns, requiring specific configuration.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"litestar","vendor":"litestar"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-185","name":"Incorrect Regular Expression"}],"description":"Litestar is an Asynchronous Server Gateway Interface (ASGI) framework. Prior to 2.20.0, in litestar.middleware.allowed_hosts, allowlist entries are compiled into regex patterns in a way that allows regex metacharacters to retain special meaning (e.g., . matches any character). This enables a bypass where an attacker supplies a host that matches the regex but is not the intended literal hostname. This vulnerability is fixed in 2.20.0.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Litestar has an AllowedHosts validation bypass due to unescaped regex metacharacters in configured host patterns","id":"CVE-2026-25479","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"FileStore key canonicalization collisions allow response cache mixup/poisoning (ASCII ord + Unicode NFKD)","id":"CVE-2026-25480"},"packages":[{"ecosystem":"PyPI","fixed":["2.20.0"],"introduced":["0"],"last_affected":[],"package":"litestar","purl":"pkg:pypi/litestar","source":"PYSEC-2026-2196"},{"ecosystem":"PyPI","fixed":["2.20.0"],"introduced":["2.19.0"],"last_affected":[],"package":"litestar","purl":null,"source":"GHSA-93ph-p7v4-hwh4"},{"ecosystem":"PyPI","fixed":["2.20.0"],"introduced":["2.19.0"],"last_affected":[],"package":"litestar","purl":"pkg:pypi/litestar","source":"GHSA-93ph-p7v4-hwh4"}],"prev":{"headline":"Litestar has a CORS origin allowlist bypass due to unescaped regex metacharacters in allowed origins","id":"CVE-2026-25478"},"products":["litestar"],"published":"2026-02-09","related":[{"cvss_score":8.2,"headline":"Litestar allows unbounded resource consumption (DoS vulnerability)","id":"CVE-2024-52581","kev_date_added":null,"published":"2024-11-20"},{"cvss_score":7.4,"headline":"Litestar has a CORS origin allowlist bypass due to unescaped regex metacharacters in allowed origins","id":"CVE-2026-25478","kev_date_added":null,"published":"2026-02-09"},{"cvss_score":6.5,"headline":"FileStore key canonicalization collisions allow response cache mixup/poisoning (ASCII ord + Unicode NFKD)","id":"CVE-2026-25480","kev_date_added":null,"published":"2026-02-09"}],"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":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-10","vendors":["litestar-org"]},"summary":"Attackers can bypass host validation in Litestar by exploiting unescaped regex metacharacters in allowlist patterns, requiring specific configuration.","url":"https://insights.sbomify.com/CVE-2026-25479/"}