dbcve.org
TwigFramework / library · Symfony

CVE-2026-48808

HIGH · 7.5 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 3.27.0 or later.
See remediation →
84/100
Remediation priority · High
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 column filter passes the active sandbox state as a boolean but does not forward the current Source to SandboxExtension::checkPropertyAllowed(), so SourcePolicyInterface decisions are lost and a template author can read public or magic properties not allowed by 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 versions prior to 3.27.0 contain a sandbox bypass vulnerability in the column filter. The filter passes sandbox state as a boolean but fails to forward the Source context to SandboxExtension::checkPropertyAllowed(), causing SourcePolicyInterface decisions to be ignored. This allows template authors to read public or magic properties that should be blocked by the sandbox policy.

MitigationUpgrade Twig to version 3.27.0 or later. Review existing templates using the column filter to ensure they comply with intended sandbox restrictions after the 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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 version of twig/twig
    Affected if The version is less than 3.27.0
  2. Verify sandbox is enabled
    Check your Twig Environment configuration for sandbox extension: look for \Twig\Extension\SandboxExtension in your Twig setup, or check if 'sandbox' is included in your 'extensions' or 'autoescape' configuration
    Affected if Sandbox extension is enabled in your Twig environment
  3. Inspect templates for column filter usage
    Search your Twig templates for usage of the 'column' filter (e.g., '|column') and review whether those templates are processed within a sandbox context
    Affected if Templates use the column filter within a sandboxed template and the Twig version is below 3.27.0
  4. Review SourcePolicyInterface implementation
    If you have implemented a custom SourcePolicyInterface for sandbox restrictions, verify that your policy's property access decisions are being honored when the column filter is used
    Affected if Custom SourcePolicyInterface property restrictions are not being enforced on column filter usage

You are affected if you are using Twig version below 3.27.0 with the sandbox extension enabled and templates using the column filter that should have restricted property access.

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. Review existing templates using the column filter to ensure they comply with intended sandbox restrictions after the 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. Run `composer require twig/twig:^3.27.0` to upgrade to the fixed version
  3. Verify the upgrade was successful by running `composer show twig/twig` and confirming version 3.27.0 or higher is installed
  4. Test your application to ensure templates using the column filter and sandbox mode work correctly with the policy restrictions
Caveat No breaking changes mentioned in the advisory; the fix is a backward-compatible security patch

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 / QA1.0 h
7.0 hours of engineering $1,210
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,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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