# CVE-2024-45411: Twig has a possible sandbox bypass

> Attackers can bypass Twig sandbox restrictions to execute unauthorized code or access protected resources in PHP applications.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Sep 2024
- **Updated:** 16 Sep 2024
- **Also known as:** CLSA-2026-1783991055, DEBIAN-CVE-2024-45411, DLA-3888-1, DSA-5771-1, GHSA-6j75-5wfj-gh66, UBUNTU-CVE-2024-45411, USN-7549-1

## What is CVE-2024-45411?

CVE-2024-45411 is a high-severity vulnerability in twigphp Twig, published on 9 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Twig is a template language for PHP. Under some circumstances, the sandbox security checks are not run which allows user-contributed templates to bypass the sandbox restrictions. This vulnerability is fixed in 1.44.8, 2.16.1, and 3.14.0.

Weakness: CWE-693 (Protection Mechanism Failure)

## Which versions are affected by CVE-2024-45411?

8 open source packages ship an affected version, including twig/twig. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `twig/twig` | Packagist | From 1.0.0 | 1.44.8 |
| `twig/twig` | Packagist | From 1.0.0 | 1.44.8 |
| `twig/twig` | Packagist | From 2.0.0 | 2.16.1 |
| `twig/twig` | Packagist | From 2.0.0 | 2.16.1 |
| `twig/twig` | Packagist | From 3.0.0 | 3.11.1 |
| `twig/twig` | Packagist | From 3.0.0 | 3.11.1 |
| `twig/twig` | Packagist | From 3.12.0 | 3.14.0 |
| `twig/twig` | Packagist | From 3.12.0 | 3.14.0 |

Products: Symfony Twig.

## How do I fix CVE-2024-45411?

Upgrade twig/twig to a fixed version for your release line: 1.44.8, 2.16.1, 3.11.1 or 3.14.0.

## Is CVE-2024-45411 being exploited?

There is no known exploitation of CVE-2024-45411 in the wild and no public exploit code.

## Other vulnerabilities in twigphp Twig

- [CVE-2018-13818](https://insights.sbomify.com/CVE-2018-13818/): Code injection in n/a (critical 9.8)
- [CVE-2026-46633](https://insights.sbomify.com/CVE-2026-46633/): Twig: PHP code injection via `{% use %}` template name (high 8.7)
- [CVE-2026-46640](https://insights.sbomify.com/CVE-2026-46640/): Twig: Arbitrary PHP code execution via `_self.(<string>)` macro-reference compilation (high 8.7)
- [CVE-2026-24425](https://insights.sbomify.com/CVE-2026-24425/): Twig 2.16.x & 3.9.0-3.25.x Sandbox Bypass via SourcePolicyInterface (high 8.7)
- [CVE-2026-46634](https://insights.sbomify.com/CVE-2026-46634/): Twig: `template_from_string()` escapes a SourcePolicy-driven sandbox via synthesized template name (high 7.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-45411 and fix it if it is affected.

What it is: CVE-2024-45411 is a high-severity vulnerability in twigphp Twig, published on 9 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-45411 in the wild and no public exploit code.

Affected packages and fixed versions:
- twig/twig (Packagist): affected from 1.0.0; fixed in 1.44.8
- twig/twig (Packagist): affected from 1.0.0; fixed in 1.44.8
- twig/twig (Packagist): affected from 2.0.0; fixed in 2.16.1
- twig/twig (Packagist): affected from 2.0.0; fixed in 2.16.1
- twig/twig (Packagist): affected from 3.0.0; fixed in 3.11.1
- twig/twig (Packagist): affected from 3.0.0; fixed in 3.11.1
- twig/twig (Packagist): affected from 3.12.0; fixed in 3.14.0
- twig/twig (Packagist): affected from 3.12.0; fixed in 3.14.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-45411/ (Markdown: https://insights.sbomify.com/CVE-2024-45411/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-45411
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-45411
- OSV: https://osv.dev/vulnerability/CVE-2024-45411

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-45411/
Summaries are generated and may contain mistakes; the official description above is the record.