CVE-2026-48060
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedLitestar is an Asynchronous Server Gateway Interface (ASGI) framework. Prior to version 2.20.0, Litestar instances which use a template engine in conjunction with CSRF protection are vulnerable to HTML Injection which can be escalated to Cross Site Scripting due to the contents of the CSRF cookie being excluded from automatic escaping by the template engine when configured inline with documentation recommendations. This issue has been patched in version 2.20.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceLitestar versions prior to 2.20.0 are vulnerable to HTML Injection that can escalate to XSS when using the template engine with CSRF protection. The CSRF cookie value is not automatically escaped by the template engine when configured according to documentation recommendations, allowing attackers to inject malicious scripts via the cookie.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Litestar versionRun `pip show litestar` or execute `import litestar; print(litestar.__version__)` in PythonAffected if Version is lower than 2.20.0
-
Confirm template engine usageCheck application code for template rendering configuration, looking for TemplateConfig or similar template engine setupAffected if Templates are configured and rendered in the application
-
Verify CSRF protection is enabledInspect the application configuration for CSRF middleware or cookie configuration (look for CSRFConfig, cookie_name settings, or csrf middleware registration)Affected if CSRF protection is active and a CSRF cookie is configured
-
Check for CSRF cookie value in templatesSearch template files (.html, .jinja2, etc.) for patterns like `{{ cookie_csrf_token }}` or similar references to CSRF cookie values that may be rendered without escapingAffected if Templates contain unescaped CSRF cookie value references (using {{ }} instead of {{- -}} with explicit escaping or the |safe filter was incorrectly applied)
User is affected if Litestar version is below 2.20.0 AND the application uses both the template engine with CSRF protection where CSRF cookie values are rendered in templates without proper escaping.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Litestar to version 2.20.0 or later. This is a framework-level patch that fixes the template escaping behavior for CSRF cookie values.
litestar version 2.20.0
- 1. Identify the current Litestar version in your project by checking your dependencies (e.g., requirements.txt, pyproject.toml, or pip list)
- 2. Upgrade Litestar to version 2.20.0 or later using your package manager: pip install 'litestar>=2.20.0' or poetry update litestar
- 3. Verify the upgrade was successful by checking: pip show litestar or litestar --version
- 4. If your project uses a template engine with CSRF protection, review the updated documentation for version 2.20.0 to ensure proper configuration
- 5. Run your application's test suite to confirm the upgrade does not break existing functionality
- 6. Deploy the updated version to your environment
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-48060 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-48060 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data