dbcve.org
TwigFramework / library · Symfony

CVE-2026-46633

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 3.26.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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. Prior to 3.26.0, Compiler::string() does not escape single quotes when a template name from a {% use %} tag is placed inside a PHP single-quoted string literal, allowing a crafted template name to terminate the string and inject arbitrary PHP expressions into the compiled cache file. 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, the Compiler::string() method fails to escape single quotes when processing template names from {% use %} tags that are embedded in PHP single-quoted string literals. This allows an attacker to craft a malicious template name that breaks out of the string literal and injects arbitrary PHP expressions into compiled cache files, which are then executed by PHP.

MitigationUpgrade Twig to version 3.26.0 or later. Clear all compiled template cache files after upgrading and audit templates using the {% use %} tag for any suspicious template names.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Determine installed Twig version
    Run `composer show twig/twig` or check the version entry in your composer.lock file under twig/twig package
    Affected if The version shown is less than 3.26.0
  2. Identify templates using {% use %} tags
    Search your templates directory for files containing the pattern `{% use `
    Affected if Any .twig template files contain {% use %} tags with single-quoted template names
  3. Locate compiled template cache
    Check your Twig cache directory (commonly var/cache or similar in Symfony projects) for compiled .php template files
    Affected if Compiled PHP cache files exist from Twig templates using {% use %} tags
  4. Inspect compiled cache for injection patterns
    Open a compiled cache file corresponding to a template with {% use %} and search for unescaped single quotes around template names or unexpected PHP code
    Affected if The compiled cache file contains template names in single-quoted strings without proper escaping, or contains PHP code that appears to break out of the string literal

You are affected if Twig version is below 3.26.0 AND your templates use {% use %} tags with single-quoted template names that get compiled into the cache.

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. Clear all compiled template cache files after upgrading and audit templates using the {% use %} tag for any suspicious template names.

Recommended fix High confidence

Twig 3.26.0

  1. Identify all projects and dependencies that use Twig with versions prior to 3.26.0
  2. Update the Twig dependency in your project's composer.json or package manager to version 3.26.0 or later
  3. Run `composer update twig/twig` or equivalent package manager command to fetch the fixed version
  4. Run application tests to verify the upgrade does not break existing functionality
  5. Redeploy the updated application to production environments
Caveat Check Twig 3.26.0 changelog for any minor breaking changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Twig Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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