TwigFramework / library · Symfony
CVE-2026-46628
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 · uneditedTwig is a template language for PHP. Prior to 3.26.0, the deprecated spaceless filter is registered as safe for HTML, causing Twig autoescaping to emit attacker-controlled markup unescaped when spaceless is applied to untrusted input. This issue is fixed in version 3.26.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 confidenceThe Twig template engine prior to version 3.26.0 incorrectly marks the deprecated 'spaceless' filter as HTML-safe, bypassing autoescaping. When this filter processes untrusted input, attacker-controlled markup is emitted unescaped, enabling reflected XSS attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
TwigFramework / library
< 3.26.0CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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.
-
Determine Twig version installedRun 'composer show twig/twig' or check your composer.lock file for the twig/twig package version numberAffected if The reported version is less than 3.26.0
-
Locate Twig template filesSearch your codebase for .twig template files, typically found in templates/ or Resources/views/ directoriesAffected if Twig templates exist in your project
-
Identify spaceless filter usageSearch your Twig templates for the '|spaceless' filter syntax, for example: {{ variable|spaceless }}Affected if The spaceless filter is used in any template
-
Check if untrusted input feeds into spacelessReview templates using spaceless and trace whether any variables passed to it contain user-supplied or external data (request parameters, database content, API responses)Affected if User-controlled or untrusted data flows into the spaceless filter
You are affected if Twig version is below 3.26.0 AND the spaceless filter is applied to any user-supplied or untrusted input in your templates.
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 · scoped3.26.0
Upgrade Twig to version 3.26.0 or later. Until the upgrade is complete, avoid applying the spaceless filter to any user-supplied or untrusted input.
3.26.0
- Check current Twig version by running `composer show twig/twig` or inspecting your composer.json
- Update Twig to version 3.26.0 by running `composer require twig/twig:^3.26.0` or manually update the version constraint in composer.json
- Run `composer update twig/twig` to install the fixed version
- Clear any cached Twig templates if your application uses caching (e.g., delete cache/ or var/cache/ directories)
- Test your application to verify templates render correctly with the new version, particularly any templates using the spaceless filter
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Twig
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46628 — 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-46628 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