dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2026-46635

MEDIUM · 5.3 CVSS v4.0 Published 2026-07-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/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. Prior to 3.26.0, the column filter passes object arrays to PHP array_column(), which reads public and magic properties without reaching CoreExtension::getAttribute() or SandboxExtension::checkPropertyAllowed(), allowing an untrusted template author with column in allowedFilters to read properties that are not in the sandbox allowlist. 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

This is a sandbox bypass vulnerability in Twig's column filter. Prior to version 3.26.0, the column filter passes object arrays directly to PHP's native array_column() function, which reads public and magic properties without going through Twig's security checks (CoreExtension::getAttribute() or SandboxExtension::checkPropertyAllowed()). This allows an untrusted template author with 'column' in allowedFilters to read properties that should be blocked by the sandbox allowlist.

MitigationUpgrade to Twig 3.26.0 or later. If immediate upgrade is not feasible, ensure untrusted template authors do not have access to the 'column' filter in the sandbox allowedFilters configuration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 check your composer.lock for the twig/twig package version
    Affected if Version is lower than 3.26.0 (e.g., 3.25.0, 3.24.0, etc.)
  2. Verify sandbox extension is enabled
    Search your codebase for 'SandboxExtension' in your Twig configuration or bootstrap files (e.g., $twig->addExtension(new \Twig\Extension\SandboxExtension()))
    Affected if Sandbox is enabled and you rely on it to restrict template access
  3. Inspect allowedFilters configuration
    Look for the sandbox security policy configuration where allowedFilters are defined. Search for 'allowedFilters' containing 'column' in your Twig sandbox policy setup
    Affected if The 'column' filter is explicitly listed in the allowedFilters array of your sandbox security policy
  4. Confirm templates are authored by untrusted users
    Review whether any templates in your application are rendered with sandbox settings and come from user input, database, or external sources
    Affected if Untrusted template authors can inject templates into the sandboxed Twig environment where the column filter is allowed

You are affected if you run Twig below version 3.26.0 with the sandbox enabled and the 'column' filter included in allowedFilters for untrusted 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Twig 3.26.0 or later. If immediate upgrade is not feasible, ensure untrusted template authors do not have access to the 'column' filter in the sandbox allowedFilters configuration.

Recommended fix Moderate confidence

3.26.0

  1. Check your project's composer.json for the Twig dependency version
  2. Update Twig to version 3.26.0 by running: composer require twig/twig:^3.26.0 or composer update twig/twig
  3. Verify the update completed successfully by checking the installed version: composer show twig/twig
  4. Test that your templates using the column filter still function correctly
  5. If using SandboxExtension, verify that the column filter is properly configured in allowedFilters
Caveat Review the Twig 3.26.0 changelog for any minor behavior changes; generally safe for minor version upgrades

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

Have this fixed 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 help mitigating

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