Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Smarty versions 3 before 3.1.32 are vulnerable to PHP code injection when fetch() or display() is called on custom resources that do not sanitize the template name. The source gives few details on who can trigger it or how far an attacker could go. Upgrade smarty/smarty to 3.1.32 or later.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 9.8 | Critical | 3.0 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H | GitHub Advisory Database |
- CISA KEV Not listed.
- EPSS 0.031, the 88th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:30 UTC First seen by agentprime
- 31 Oct 2026, 14:30 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-9m49-vhwv-422g
- OSV: GHSA-9m49-vhwv-422g
- nvd.nist.gov/vuln/detail/CVE-2017-1000480
- github.com/smarty-php/smarty
- github.com/smarty-php/smarty/blob/master/change_log.txt
- lists.debian.org/debian-lts-announce/2018/01/msg00023.html
- lists.debian.org/debian-lts-announce/2018/02/msg00000.html
- www.debian.org/security/2018/dsa-4094