dbcve.org
TwigFramework / library · Symfony

CVE-2026-46637

MEDIUM · 5.4 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 3.26.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable 5 weeks old

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 · unedited
Twig is a template language for PHP. Prior to 3.26.0, several filters in twig/markdown-extra and twig/cssinliner-extra are registered with is_safe => [all], causing Twig to treat plain text or HTML output as safe in HTML, JavaScript, CSS, URL, and other contexts where the output is not properly escaped. 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 confidence

In Twig versions prior to 3.26.0, filters in twig/markdown-extra and twig/cssinliner-extra are incorrectly registered with is_safe => [all], causing the template engine to treat potentially unsafe HTML, JavaScript, CSS, or URL content as safe for output in all contexts. This can enable cross-site scripting (XSS) attacks when user-controlled markdown or CSS is processed.

MitigationUpgrade Twig to version 3.26.0 or later to resolve this vulnerability. Review any templates using markdown and cssinliner filters to ensure proper escaping is applied where needed.

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
Affected:< 3.26.0

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Twig version
    Run `composer show twig/twig` or `composer show symfony/twig-bridge` to see the installed version. Alternatively, check your composer.lock file for the twig/twig package version.
    Affected if The Twig version is earlier than 3.26.0 (e.g., 3.25.0, 3.24.0, etc.)
  2. Identify if twig/markdown-extra is installed
    Run `composer show twig/markdown-extra` or check your composer.lock for the twig/markdown-extra package. Also inspect your Twig configuration files for `MarkdownExtension` registration.
    Affected if The twig/markdown-extra package is installed in your project and you are using Twig versions prior to 3.26.0
  3. Identify if twig/cssinliner-extra is installed
    Run `composer show twig/cssinliner-extra` or check your composer.lock for the twig/cssinliner-extra package. Inspect your Twig configuration for `CssInlinerExtension` registration.
    Affected if The twig/cssinliner-extra package is installed in your project and you are using Twig versions prior to 3.26.0
  4. Check for use of markdown filters in templates
    Search your Twig templates for uses of the `|markdown` filter (e.g., `{{ content|markdown }}`) or the `|md` filter. Also check for `{% markdown %}` block usage.
    Affected if Your templates process user-controlled input through the markdown or md filter and your Twig version is below 3.26.0
  5. Check for use of cssinliner filters in templates
    Search your Twig templates for uses of the `|cssinliner` filter (e.g., `{{ html|cssinliner }}`). This is commonly used in email template processing.
    Affected if Your templates process content through the cssinliner filter and your Twig version is below 3.26.0

You are affected if you have Twig versions prior to 3.26.0 AND are using either the twig/markdown-extra or twig/cssinliner-extra packages with their filters on user-controlled input.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 3.26.0 or later
Fixed in 3.26.0
Interim mitigation

Upgrade Twig to version 3.26.0 or later to resolve this vulnerability. Review any templates using markdown and cssinliner filters to ensure proper escaping is applied where needed.

Recommended fix High confidence

Twig version 3.26.0

  1. 1. Check the current Twig version installed in your project (e.g., via composer show twig/twig or your lock file)
  2. 2. Update Twig to version 3.26.0 or later using composer: composer require twig/twig:^3.26.0
  3. 3. Run composer update to install the fixed version
  4. 4. Clear any application caches that may contain compiled Twig templates
  5. 5. Test your application, particularly pages using twig/markdown-extra and twig/cssinliner-extra filters, to ensure content renders correctly
  6. 6. Verify that any templates using these filters properly escape output in HTML, JavaScript, CSS, or URL contexts where needed

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 / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46637 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46637 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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