~ / search / GHSA-2q52-x2ff-qgfr

GHSA-2q52-x2ff-qgfr

Twig: Possible sandbox bypass when using a source policy

Source: GitHub Advisory Database (reviewed) High CVE-2026-24425

Packages

EcosystemPackageAffectedFixed in
Packagist twig/twig >= 2.16.0, <= 2.16.1 no fix listed
Packagist twig/twig >= 3.9.0, < 3.26.0 3.26.0

Details

As written in the advisory (Markdown source, shown as plain text).

# Description When using the sandbox with a `SourcePolicyInterface`, Twig does not always apply the sandbox restriction that forbids non-`Closure` callbacks for callback-accepting filters. The issue affects the `sort`, `filter`, `map`, and `reduce` filters. In the affected versions, the runtime check that rejects non-`Closure` callbacks in sandbox mode does not use the current template `Source`. As a result, when the sandbox is enabled through a source policy instead of being enabled globally, Twig can incorrectly treat the current execution as non-sandboxed for these callback checks. This can allow user-controlled templates to pass arbitrary PHP callables to callback-accepting filters even though the template is being sandboxed through a source policy. The issue happens when all these conditions are met: - The sandbox is not enabled globally; - A `SourcePolicyInterface` enables the sandbox for the rendered template; - The template uses one of the `sort`, `filter`, `map`, or `reduce` filters; - The callback is not a `Closure`. # Resolution The patch makes callback sandbox checks source-aware by propagating the current template `Source` to callback-accepting filters and using it when deciding whether sandbox restrictions apply. # Credits We would like to thank XavLim and Wade Sparks for reporting the issue and Fabien Potencier for fixing the issue.

References

External links from the advisory. They lead to third-party sites.