Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Smarty (smarty/smarty) versions 5.0.0 before 5.8.4 are affected, with the fix in 5.8.4. An attacker who can supply template content that is rendered with Smarty Security enabled can use the built-in stream resource type to bypass the stream restrictions and read local files that the PHP process can access. Upgrade to smarty/smarty 5.8.4 or later. The source gives no workaround beyond upgrading.
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 |
|---|---|---|---|---|
| 6.9 | Medium | 4.0 | CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0051, the 43rd percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:24 UTC First seen by agentprime
- 31 Oct 2026, 14:24 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-rjhh-76wf-8xmw
- OSV: GHSA-rjhh-76wf-8xmw
- github.com/smarty-php/smarty/security/advisories/GHSA-rjhh-76wf-8xmw
- github.com/smarty-php/smarty/pull/1195
- github.com/smarty-php/smarty/commit/3c9f77a2e06ce319ae0092496af32cc8f3adc52e
- github.com/smarty-php/smarty
- github.com/smarty-php/smarty/releases/tag/v5.8.4