Summary
Twig has a possible sandbox bypass
Description
Under some circumstances, the sandbox security checks are not run which allows user-contributed templates to bypass the sandbox restrictions.
The security issue happens when all these conditions are met:
- The sandbox is disabled globally;
- The sandbox is enabled via a sandboxed
include()function which references a template name (likeincluded.twig) and not aTemplateorTemplateWrapperinstance; - The included template has been loaded before the
include()call but in a non-sandbox context (possible as the sandbox has been globally disabled).
Resolution
The patch ensures that the sandbox security checks are always run at runtime.
Credits
We would like to thank Fabien Potencier for reporting and fixing the issue.
Impact
CVE-2024-45411 has a CVSS score of 8.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.44.8, 2.16.1, 3.14.0, 3.11.1); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
twig/twig to 1.44.8 or later; twig/twig to 2.16.1 or later; twig/twig to 3.14.0 or later; twig/twig to 3.11.1 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2024-45411? CVE-2024-45411 is a medium-severity security vulnerability in twig/twig (composer), affecting versions >= 1.0.0, < 1.44.8. It is fixed in 1.44.8, 2.16.1, 3.14.0, 3.11.1.
- How severe is CVE-2024-45411? CVE-2024-45411 has a CVSS score of 8.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of twig/twig are affected by CVE-2024-45411? twig/twig (composer) versions >= 1.0.0, < 1.44.8 is affected.
- Is there a fix for CVE-2024-45411? Yes. CVE-2024-45411 is fixed in 1.44.8, 2.16.1, 3.14.0, 3.11.1. Upgrade to this version or later.
- Is CVE-2024-45411 exploitable, and should I be worried? Whether CVE-2024-45411 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2024-45411 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2024-45411?
- Upgrade
twig/twigto 1.44.8 or later - Upgrade
twig/twigto 2.16.1 or later - Upgrade
twig/twigto 3.14.0 or later - Upgrade
twig/twigto 3.11.1 or later
- Upgrade