CVE-2022-39261

Twig may load a template outside a configured directory when using the filesystem loader

Description

When using the filesystem loader to load templates for which the name is a user input, it is possible to use the source or include statement to read arbitrary files from outside the templates directory when using a namespace like @somewhere/../some.file (in such a case, validation is bypassed).

Resolution

We fixed validation for such template names.

Even if the 1.x branch is not maintained anymore, a new version has been released.

Credits

We would like to thank Dariusz Tytko for reporting the issue and Fabien Potencier for fixing the issue.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2022-39261 has a CVSS score of 7.5 (High). The vector is network-reachable, no 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.7, 2.15.3, 3.4.3); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2022-39261? CVE-2022-39261 is a high-severity path traversal vulnerability in twig/twig (composer), affecting versions >= 1.0.0, < 1.44.7. It is fixed in 1.44.7, 2.15.3, 3.4.3. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2022-39261? CVE-2022-39261 has a CVSS score of 7.5 (High). 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.
3. Which versions of twig/twig are affected by CVE-2022-39261? twig/twig (composer) versions >= 1.0.0, < 1.44.7 is affected.
4. Is there a fix for CVE-2022-39261? Yes. CVE-2022-39261 is fixed in 1.44.7, 2.15.3, 3.4.3. Upgrade to this version or later.
5. Is CVE-2022-39261 exploitable, and should I be worried? Whether CVE-2022-39261 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
6. What actually determines whether CVE-2022-39261 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.
7. How do I fix CVE-2022-39261?
   • Upgrade twig/twig to 1.44.7 or later
   • Upgrade twig/twig to 2.15.3 or later
   • Upgrade twig/twig to 3.4.3 or later

Other vulnerabilities in twig/twig