First published: Sun Jan 24 2021(Updated: )
Sandbox protection could be bypassed through access to an internal Smarty object that should have been blocked. Sites that rely on [Smarty Security features](https://www.smarty.net/docs/en/advanced.features.tpl) should upgrade as soon as possible. Please upgrade to 3.1.39 or higher.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
composer/smarty/smarty | <=3.1.38 | |
debian/smarty3 | 3.1.33+20180830.1.3a78a21f+selfpack1-1+deb10u1 3.1.33+20180830.1.3a78a21f+selfpack1-1+deb10u2 3.1.39-2+deb11u1 3.1.47-2 3.1.48-1 | |
composer/smarty/smarty | <3.1.39 | 3.1.39 |
Smarty | <3.1.39 | |
Debian | =9.0 | |
Debian | =10.0 | |
Debian | =11.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2021-26119 is considered a critical vulnerability that allows sandbox protection to be bypassed.
To fix CVE-2021-26119, upgrade Smarty to version 3.1.39 or higher.
Smarty versions up to and including 3.1.38 are affected by CVE-2021-26119.
CVE-2021-26119 affects systems using affected versions of Smarty, including various Debian releases.
CVE-2021-26119 compromises Smarty's security features by allowing unauthorized access to internal Smarty objects.