Quick answers
- Is CVE-2026-48060 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-48060 being exploited in the wild.
- How severe is CVE-2026-48060?
- High severity, with a CVSS score of 8.1, published 28 July 2026.
- Which products and versions are affected?
- litestar (PyPI) < 2.22.0, ECOSYSTEM:introduced=0,fixed=2.22.0.
- Is there a fix for CVE-2026-48060?
- Yes. litestar (PyPI): upgrade to 2.22.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-48060 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-48060?
- Check whether you run litestar (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- litestar (PyPI): upgrade to 2.22.0 or later
pip install "litestar>=2.22.0"
Technical details
A Cross-Site Scripting (XSS) vulnerability exists in Litestar when using a template engine (such as Jinja2, Mako, or MiniJinja) alongside CSRF protection. The root cause is that the `csrf_input` variable, which contains the CSRF token from a cookie, is marked as 'safe' or otherwise excluded from automatic HTML escaping when following standard documentation examples. An attacker can poison the `csrftoken` cookie with malicious HTML or JavaScript. If a victim visits a site on the same top-level domain that sets this cookie and is then redirected to the vulnerable Litestar application, the payload will execute in the victim's browser context. This allows for session hijacking or arbitrary actions on behalf of the user. The vulnerability is addressed in version 2.20.0.
Affected products
- litestar-org Litestar < 2.20.0
Identifiers
- CVE-2026-48060
- GHSA-542p-wvx7-72m4
- PYSEC-2026-2604
Timeline
- 2026-05-20: advisory: GitHub Security Advisory GHSA-542p-wvx7-72m4 published
- 2026-07-28: disclosed: CVE-2026-48060 published to NVD
- 2026-02-08: patched: Version 2.20.0 released