# Twig: Sandbox property allowlist bypass via the \`column\` filter (array_column on objects)

Advisory record · `GHSA-vcc8-phrv-43wj`

- **Identifiers:** `GHSA-vcc8-phrv-43wj` · `CVE-2026-46635` · `PKSA-n14z-jjjg-g8vd`
- **State:** Confirmed
- **Severity:** CVSS 5.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 21 May 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 21 May 2026, 21:25 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `twig/twig` (Packagist): affected `<3.26.0`; fixed in `3.26.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Twig (Packagist twig/twig) versions before 3.26.0 are affected. When the sandbox is enabled, a template author who has been allowed to use the \`column\` filter can read public or magic properties of objects in the render context, bypassing the sandbox's property allowlist. The source describes this as a variant of CVE-2024-51755 that the earlier fix did not cover. Upgrade to twig/twig 3.26.0, which enforces the property allowlist for the \`column\` filter.

Written 31 Oct 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.3 Medium, CVSS 4.0: `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`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0033, the 26th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 20 May 2026, 07:44 UTC: [Published by the maintainers as a GitHub repository advisory](https://github.com/twigphp/Twig/security/advisories/GHSA-vcc8-phrv-43wj)
- 31 Oct 2026, 14:01 UTC: First seen by agentprime
- 31 Oct 2026, 14:01 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-vcc8-phrv-43wj)

## Sources

- [GitHub Advisory Database: GHSA-vcc8-phrv-43wj](https://github.com/advisories/GHSA-vcc8-phrv-43wj)
- [OSV: GHSA-vcc8-phrv-43wj](https://osv.dev/vulnerability/GHSA-vcc8-phrv-43wj)
- <https://github.com/twigphp/Twig/security/advisories/GHSA-vcc8-phrv-43wj>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/twig/twig/CVE-2026-46635.yaml>
- <https://github.com/twigphp/Twig>
- <https://symfony.com/cve-2026-46635>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-vcc8-phrv-43wj>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-vcc8-phrv-43wj/>. Everything for agents: <https://agentprime.io/llms.txt>.
