dbcve.org
TwigFramework / library · Symfony

CVE-2026-46639

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 3.26.0 or later.
See remediation →
71/100
Remediation priority · Elevated
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.24.0 until 3.26.0, object-destructuring assignment compiles CoreExtension::getAttribute() with the sandbox argument hardcoded to false, disabling property and method policy checks and allowing an attacker with write access to a sandboxed Twig template to read public properties or invoke public getters on objects passed to the template engine. 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.24.0 through 3.26.0 contain a sandbox bypass vulnerability in object-destructuring assignment where the CoreExtension::getAttribute() function compiles with the sandbox argument hardcoded to false, disabling policy checks and allowing a template attacker to read public properties or invoke public methods on sandboxed objects.

MitigationUpgrade Twig to version 3.26.0 or later to resolve the hardcoded sandbox argument, and audit any sandboxed templates for unauthorized access patterns.

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.24.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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 inspect your composer.lock file to find the installed twig/twig version number
    Affected if The version is >= 3.24.0 and < 3.26.0
  2. Verify sandbox is in use
    Check your Twig configuration for the sandbox extension being enabled, or look for 'Twig\Extension\SandboxExtension' in your code. Also check if any templates are rendered with the sandbox security policy via $twig->render($template, $context, ['sandbox'])?> or similar patterns
    Affected if Sandbox mode is enabled and applied to template rendering
  3. Inspect templates for object-destructuring syntax
    Search template files for the destructuring assignment pattern such as {% set {property} = object %} or {% set {foo, bar} = obj %} which triggers the vulnerable code path in CoreExtension::getAttribute()
    Affected if Templates contain object-destructuring assignment syntax on sandboxed objects
  4. Check for access to sandboxed object properties/methods
    Audit templates that use the sandbox extension for patterns like {{ sandboxedObject.property }} or {{ sandboxedObject.method() }} where the object originates from a sandboxed context
    Affected if Templates access properties or methods on objects that are wrapped by the sandbox extension

You are affected if your Twig version is between 3.24.0 and 3.26.0 AND you use the sandbox extension with object-destructuring assignment in your templates.

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 the hardcoded sandbox argument, and audit any sandboxed templates for unauthorized access patterns.

Recommended fix High confidence

3.26.0

  1. Check current Twig version by running `composer show twig/twig` or checking your composer.json
  2. Update composer.json to require Twig version ^3.26.0 by changing the twig/twig requirement
  3. Run `composer update twig/twig` to install the fixed version
  4. Verify the installed version is 3.26.0 by running `composer show twig/twig`
  5. Test your application to ensure the upgrade does not break existing functionality

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-46639 — 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-46639 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