TwigFramework / library · Symfony
CVE-2026-46638
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, {% sandbox %}{% include %} can include a template that was previously loaded outside the sandbox without re-invoking checkSecurity(), allowing the cached template to use tags, filters, and functions that should have been denied by SecurityPolicy::checkSecurity(). 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 confidenceTwig's sandbox mode has a security bypass where {% sandbox %}{% include %} can load a template that was previously cached outside the sandbox without re-invoking checkSecurity(), allowing blocked tags, filters, and functions to execute despite SecurityPolicy restrictions.
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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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.
-
Determine installed Twig versionRun 'composer show symfony/twig-bridge' or check the version field in vendor/symfony/twig-bridge/composer.jsonAffected if The version displayed is less than 3.26.0
-
Identify if sandbox mode is enabledSearch codebase for instances of SecurityPolicy class instantiation, or grep templates for '{% sandbox %}' tagsAffected if Twig SecurityPolicy is actively used to restrict tags, filters, or functions in your application
-
Verify template caching configurationCheck Twig environment configuration for cache settings, typically in config/packages/twig.yaml or similar, and identify where cached templates are storedAffected if Templates are cached to disk and {% include %} is used within sandboxed templates
-
Confirm use of {% include %} inside sandbox blocksSearch templates for patterns like '{% sandbox %}' followed by '{% include %}'Affected if You have templates that use {% sandbox %}{% include %} to load other templates
You are affected if using Twig versions before 3.26.0 with sandbox mode enabled and using {% sandbox %}{% include %} to load templates that may be cached outside the sandbox context.
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 to Twig version 3.26.0 or later to apply the security fix.
Twig 3.26.0
- Check the current Twig version in your project (e.g., run `composer show twig/twig` or inspect your composer.json)
- Update the Twig dependency to version 3.26.0 or later by running `composer require twig/twig:^3.26.0` or `composer update twig/twig`
- Verify the installed version is 3.26.0 or higher using `composer show twig/twig`
- Test your application's sandbox functionality to confirm {% sandbox %} and {% include %} work correctly with the SecurityPolicy restrictions enforced
- Ensure any cached templates are cleared to avoid using old cached versions
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Twig
Scoped from the published advisory
- 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-46638 — 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-46638 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