CVE-2026-46627·PHP vulnerability
Twig is a template language for PHP. Prior to 3.26.0, the Twig sandbox does not prevent a template from consuming CPU, memory, or wall-clock time, even under the strictest allow-list, allowing untrusted templates to cause resource exhaustion. This issue is addressed in version 3.26.0 by documenting that the sandbox does not protect against resource exhaustion.
- Severity
- medium
- Software
- PHP
- Fixed in
- 3.26.0
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.39% — higher than 31% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Affected versions
Until: 3.26.0
Fixed in: 3.26.0
How to fix this CVE
Update PHP and the Twig templating engine to version 3.26.0 or later to address resource exhaustion vulnerabilities in the sandbox environment. Organizations using untrusted or user-supplied Twig templates should prioritize this update and consider implementing additional resource limits at the application or system level. While the sandbox itself cannot fully prevent CPU, memory, or execution time abuse, the patched version includes critical security documentation and improvements to mitigate these risks.
sudo dnf update phpDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check the installed PHP version and Twig version by running `php -v` and `composer show symfony/twig-bundle` or `grep -r 'Twig' /path/to/vendor/`
- Step 2: Identify if your application processes untrusted templates by searching code for `Twig_Environment` or `twig.sandbox` configuration in framework files
- Step 3: Review application logs and system resource monitoring (memory, CPU) for anomalous spikes during template processing, particularly when handling user-uploaded or dynamically-loaded templates
- Step 4: Verify the Twig version is 3.26.0 or higher by running `php -r "echo (new ReflectionClass('Twig\Environment'))->getFileName();"` and checking vendor directory timestamps post-update
FAQ
What is CVE-2026-46627?
This vulnerability describes a weakness in Twig's sandbox mode that fails to enforce resource consumption limits, allowing malicious or poorly-written templates to exhaust CPU, memory, or execution time. The fix in version 3.26.0 adds security documentation and remediation strategies rather than architectural sandbox changes.
Is CVE-2026-46627 being actively exploited?
No, this vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog and has no confirmed public exploits available.
What versions of PHP are affected by CVE-2026-46627?
All PHP versions bundled with Twig prior to version 3.26.0 are affected. This primarily impacts Symfony framework versions using vulnerable Twig releases.
How do I check if my server is vulnerable to CVE-2026-46627?
Run `composer show symfony/twig-bundle | grep Version` or check `/vendor/symfony/twig-bundle/composer.json`. If Twig version is below 3.26.0, the server is vulnerable.
Does Defensia detect CVE-2026-46627?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If PHP and Twig are installed on a monitored server, CVE-2026-46627 will appear in your dashboard with remediation steps.
Related PHP CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-46627. Free for 1 server.
Get started free