dbcve.org
TwigFramework / library · Symfony

CVE-2026-24425

CRITICAL · 9.9 CVSS v3.1 Published 2026-05-20
Fix available
A fix is available. Upgrade to 3.26.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 versions 2.16.x and 3.9.0 through 3.25.x contain a sandbox bypass vulnerability when using a SourcePolicyInterface that allows attackers with template rendering capabilities to pass arbitrary PHP callables to sort, filter, map, and reduce filters. Attackers can exploit the runtime check that fails to use the current template source to bypass sandbox restrictions and execute arbitrary code when the sandbox is enabled through a source policy rather than globally.

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 2.16.x and 3.9.0 through 3.25.x contain a sandbox bypass via SourcePolicyInterface. The runtime check fails to use the current template source, allowing attackers with template rendering capabilities to pass arbitrary PHP callables to sort, filter, map, and reduce filters, bypassing sandbox restrictions and achieving arbitrary code execution when the sandbox is enabled through a source policy rather than globally.

MitigationUpgrade Twig to a patched version beyond 3.25.x, or alternatively ensure the sandbox is enabled globally rather than through SourcePolicyInterface until a patch is available.

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:>= 2.16.0, <= 2.16.1>= 3.9.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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 in PHP code: `echo Twig\Environment::VERSION;`
    Affected if version is 2.16.0, 2.16.1, or between 3.9.0 and 3.25.x inclusive
  2. Locate SourcePolicyInterface implementation
    Search project codebase for classes implementing `Twig\Sandbox\SourcePolicyInterface`
    Affected if a custom SourcePolicyInterface class is found in the project
  3. Confirm sandbox is not enabled globally
    Check configuration files (e.g., config/packages/twig.yaml in Symfony) for `sandbox: ~` or `enabled: true` at the global Environment level, not just per-template
    Affected if the sandbox is NOT enabled globally and SourcePolicyInterface is in use
  4. Identify use of affected filters with dynamic callables
    Search templates for sort, filter, map, or reduce filters used with dynamic/variable callables, e.g., `|sort(_context.callback)` or `|filter(_context.func)`
    Affected if templates pass variable or dynamic callables to these filters without strict sandbox controls
  5. Verify template rendering privileges
    Determine if untrusted users can control template rendering or template content (via user input passed to render(), include, or dynamic template loading)
    Affected if users can influence which templates are rendered or provide template content

If Twig version falls within the affected range AND SourcePolicyInterface is configured AND the sandbox is not enabled globally AND user-controlled templates or dynamic callables are used with sort/filter/map/reduce filters, the environment is vulnerable.

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 a patched version beyond 3.25.x, or alternatively ensure the sandbox is enabled globally rather than through SourcePolicyInterface until a patch is available.

Recommended fix High confidence

Twig 3.26.0 or later (for 3.x branch); Twig 2.16.2 or later (for 2.x branch)

  1. 1. Identify the current Twig version in your project by checking your composer.json or lock file
  2. 2. If using Twig 3.x (version 3.9.0 to 3.25.x), upgrade to version 3.26.0 or later
  3. 3. If using Twig 2.x (version 2.16.0 to 2.16.1), upgrade to version 2.16.2 or later
  4. 4. Run composer update twig/twig to apply the changes
  5. 5. Verify the upgrade was successful by checking the installed Twig version
  6. 6. Test your application's template rendering functionality, especially any code using sort, filter, map, or reduce filters with the sandbox enabled
  7. 7. Confirm that sandbox restrictions are properly enforced after the upgrade
Caveat Minor: Verify custom SourcePolicyInterface implementations still work correctly after upgrade, as the runtime check behavior has changed

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

Fix this in Twig Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
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,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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