Is smarty/smarty 2.6 vulnerable?
Composer · 9 releases from 2.6.24 to 2.6.33 · latest smarty/smarty is 5.8.5 · checked 2 Nov 2026
Yes: 15 known advisories
Yes. smarty/smarty 2.6.33, the last 2.6 release, is affected by 15 known security advisories (2 critical, 7 high, 6 medium), including CVE-2011-1028, CVE-2021-26120, CVE-2023-28447. Upgrade to 4.5.7 or later to fix all of them.
composer require smarty/smarty:^4.5.7Advisories affecting smarty/smarty 2.6.33
Smarty: SSRF via redirect bypass of trusted_uri using {fetch}
- Affected
- >=5.0.0 <5.8.2 · <4.5.7
- Fixed in
- 4.5.7, 5.8.2
Smarty: Symlink path traversal out of trusted directories
- Affected
- >=5.0.0 <5.8.2 · <4.5.7
- Fixed in
- 4.5.7, 5.8.2
smarty Cross-site Scripting vulnerability in Javascript escaping
- Affected
- >=4.0.0 <4.3.1 · <3.1.48
- Fixed in
- 3.1.48, 4.3.1
Smarty Cross-site Scripting vulnerability in pages that use smarty_function_mailto
- Affected
- <3.1.47 · >=4.0.0 <4.2.1
- Fixed in
- 3.1.47, 4.2.1
PHP Code Injection by malicious block or filename in Smarty
- Affected
- <3.1.45 · >=4.0.0 <4.1.1
- Fixed in
- 3.1.45, 4.1.1
Cross-site Scripting in SmartyException
- Affected
- <3.1.12
- Fixed in
- 3.1.12
Smarty arbitrary PHP code execution
- Affected
- <3.1.21
- Fixed in
- 3.1.21
Smarty Path Traversal Vulnerability
- Affected
- <3.1.33
- Fixed in
- 3.1.33
Smarty Path Traversal Vulnerability
- Affected
- <3.1.33
- Fixed in
- 3.1.33
Smarty Does Not Consider Umask Values When Setting Permissions
- Affected
- <3.0.0-beta4
- Fixed in
- 3.0.0-beta4
Smarty3 Arbitrary PHP Code Execution
- Affected
- <3.0.7
- Fixed in
- 3.0.7
Access to restricted PHP code by dynamic static class access in smarty
- Affected
- <3.1.43 · >=4.0.0 <4.0.3
- Fixed in
- 3.1.43, 4.0.3
Sandbox Escape by math function in smarty
- Affected
- <3.1.42 · >=4.0.0 <4.0.2
- Fixed in
- 3.1.42, 4.0.2
Sandbox escape through template_object in smarty
- Affected
- <3.1.39
- Fixed in
- 3.1.39
PHP Code Injection by malicious function name in smarty
- Affected
- <3.1.39
- Fixed in
- 3.1.39
Which of your client projects are still on smarty/smarty 2.6?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact smarty/smarty version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other smarty/smarty versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.