# Twig: Sandbox property and method bypass via object-destructuring assignment

Advisory record · `GHSA-mm6w-gr99-p3jj`

- **Identifiers:** `GHSA-mm6w-gr99-p3jj` · `CVE-2026-46639` · `PKSA-hgmw-wn4d-hpcy`
- **State:** Confirmed
- **Severity:** CVSS 7.1 High
- **Critical:** No
- **Weakness (CWE):** [CWE-693](https://cwe.mitre.org/data/definitions/693.html)
- **Tags:** [CWE-693](https://agentprime.io/advisories/tag/cwe-693.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:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `twig/twig` (Packagist): affected `>=3.24.0, <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 3.24.0 up to but not including 3.26.0 are affected. In these versions, the object-destructuring assignment syntax does not enforce the sandbox's property and method policy checks, even when a sandbox is active. An attacker who can write sandboxed Twig templates could read public properties or call public getters on objects passed to the engine, bypassing SecurityPolicy restrictions; the source notes this works where the do tag is allowed. Upgrade to Twig 3.26.0 or later, which forwards the sandbox flag so the policy checks are enforced.

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

- 7.1 High, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0039, the 33rd percentile, on 9 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-mm6w-gr99-p3jj)
- 31 Oct 2026, 13:58 UTC: First seen by agentprime
- 31 Oct 2026, 13:58 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-mm6w-gr99-p3jj)

## Sources

- [GitHub Advisory Database: GHSA-mm6w-gr99-p3jj](https://github.com/advisories/GHSA-mm6w-gr99-p3jj)
- [OSV: GHSA-mm6w-gr99-p3jj](https://osv.dev/vulnerability/GHSA-mm6w-gr99-p3jj)
- <https://github.com/twigphp/Twig/security/advisories/GHSA-mm6w-gr99-p3jj>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/twig/twig/CVE-2026-46639.yaml>
- <https://github.com/twigphp/Twig>
- <https://symfony.com/cve-2026-46639>

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-mm6w-gr99-p3jj>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-mm6w-gr99-p3jj/>. Everything for agents: <https://agentprime.io/llms.txt>.