CVE-2026-46640
Twig RCE via unvalidated dynamic macro names in versions 3.15.0–<3.26.0
Is CVE-2026-46640 being exploited?
Not confirmed. CVE-2026-46640 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.64% probability of exploitation in the next 30 days.
How severe is CVE-2026-46640?
CVE-2026-46640 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-46640?
Yes. A fix has been recorded for CVE-2026-46640. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-46640 affect?
CVE-2026-46640 affects Twig >=3.15.0 and <3.26.0 (PHP template engine). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-46640?
Upgrade Twig to >=3.26.0 and sanitize/untrust template inputs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution: attacker-controlled string injected into macro name causes raw PHP to be emitted and executed at template-load time.
Patch when possible
- affected>= 3.15.0 and < 3.26.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.