dbcve.org
TwigFramework / library · Symfony

CVE-2026-46640

HIGH · 8.8 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 3.26.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click 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. From 3.15.0 until 3.26.0, _self.(<string>) and import-alias dynamic attribute syntax can concatenate an attacker-controlled string into a MacroReferenceExpression name without identifier validation, causing raw PHP to be emitted into the generated template source and executed at template-load time. 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

Twig versions 3.15.0 through 3.26.0 fail to validate identifiers in dynamic attribute syntax (_self.(<string>) and import-alias). This allows an attacker-controlled string to be concatenated into a MacroReferenceExpression name, causing raw PHP to be emitted into the generated template source and executed at template-load time, resulting in arbitrary PHP code execution.

MitigationUpgrade Twig to version 3.26.0 or later. Identify all applications using affected Twig versions and update the dependency via Composer or package manager, then verify templates function correctly.

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.15.0, < 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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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. Identify installed Twig version
    Run 'composer show twig/twig' or check the version listed in your composer.lock file under twig/twig
    Affected if The version is >= 3.15.0 and < 3.26.0
  2. Locate Twig templates in the project
    Search for .html.twig, .twig, or template files in your views/templates directories and the vendor/twig/twig directory
    Affected if Templates exist and Twig is used as the templating engine
  3. Search for dynamic attribute syntax usage
    Grep your template files for patterns '_self.(' and 'import from' or 'use' statements with dynamic expressions
    Affected if Templates contain _self.(<expression>) constructs or import statements where the alias could be attacker-controlled
  4. Verify template compilation occurs at runtime
    Check if templates are rendered dynamically or cached in a location accessible to the application user
    Affected if Templates are compiled on-demand without pre-validation of all input expressions
  5. Confirm PHP code execution impact
    Review that the template engine processes user-supplied strings into MacroReferenceExpression names during template loading
    Affected if User input or untrusted data can flow into the dynamic attribute syntax positions in templates

You are affected if your installed Twig version is between 3.15.0 and 3.26.0 AND your application processes templates containing the vulnerable dynamic attribute syntax with potentially attacker-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. Identify all applications using affected Twig versions and update the dependency via Composer or package manager, then verify templates function correctly.

Recommended fix High confidence

3.26.0

  1. Upgrade Twig from any version >= 3.15.0 and < 3.26.0 to version 3.26.0 or later by running `composer require twig/twig:^3.26.0` or updating your composer.json

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
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,360
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,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46640 — 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-46640 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