dbcve.org
TwigFramework / library · Symfony

CVE-2026-48807

CRITICAL · 9.1 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 3.27.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.27.0, the sandbox __toString() checks do not fully cover Traversable values passed to join and replace filters or operands evaluated by the in and not in operators, allowing contained Stringable objects to be coerced to strings without consulting the sandbox policy. This issue is fixed in version 3.27.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's sandbox security mechanism has a bypass vulnerability where Traversable values passed to join/replace filters or evaluated by in/not in operators can coerce Stringable objects to strings without consulting the sandbox policy, allowing sandboxed templates to potentially execute restricted operations.

MitigationUpgrade Twig to version 3.27.0 or later to apply the sandbox security fix.

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.27.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
None

CVSS:3.1/AV:N/AC:L/PR:N/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 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 in your `vendor/twig/twig/composer.json` file
    Affected if The installed version is lower than 3.27.0 (e.g., 3.26.x, 3.25.x, etc.)
  2. Verify if sandbox security is enabled
    Look for Sandbox extension configuration in your Twig setup: check for `Twig\Extension\SandboxExtension` being added to your Twig environment, or look for `$twig = new \Twig\Environment(...)` followed by `$twig->addExtension(new \Twig\Extension\SandboxExtension($policy, $sandboxed))`
    Affected if Sandbox extension is enabled and actively restricting template operations
  3. Identify templates using join or replace filters with external data
    Search your Twig templates for `|join` and `|replace` filters applied to variables that may contain Traversable objects from user-controlled sources (e.g., `{{ items|join(',') }}` where items comes from request/database)
    Affected if Sandbox-enabled templates pass Traversable values to join or replace filters with data from untrusted sources
  4. Identify templates using in/not in operators with Stringable objects
    Search your Twig templates for `in` or `not in` operators used with objects that implement `__toString()` or `Stringable` interface, especially when comparing against user-provided collections
    Affected if Sandbox-enabled templates use in/not in operators with Stringable objects from untrusted sources

You are affected if you are running Twig version below 3.27.0 AND have sandbox security enabled with templates that use join/replace filters or in/not in operators on Traversable/Stringable data from potentially untrusted sources.

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.27.0 or later
Fixed in 3.27.0
Interim mitigation

Upgrade Twig to version 3.27.0 or later to apply the sandbox security fix.

Recommended fix High confidence

Twig 3.27.0

  1. Check your current Twig version by running `composer show twig/twig` or checking your composer.json
  2. Update Twig to version 3.27.0 by running `composer require twig/twig:^3.27.0` or `composer update twig/twig`
  3. Verify the upgrade was successful by running `composer show twig/twig` and confirming the version is 3.27.0 or higher
  4. Test your application to ensure the sandbox functionality works as expected with the new version

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

Fix this in Twig Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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