{"id":"CVE-2026-62996","aliases":["EUVD-2026-54499","GHSA-rjhh-76wf-8xmw","UBUNTU-CVE-2026-62996"],"status":"published","title":"Smarty Security stream restriction bypass through stream: resource","description":"Smarty is a template engine for PHP, facilitating the separation of presentation (HTML/CSS) from application logic. From 5.0.0 until 5.8.4, Smarty's stream: resource-name handling does not adequately restrict which PHP stream wrappers and filter chains can be referenced from a template, allowing a php://filter-wrapped resource name to be used to read the contents of arbitrary local files accessible to the PHP process. An attacker able to author or influence a template's resource reference could exploit this to disclose sensitive file contents outside the intended template/config scope. This issue is fixed in version 5.8.4.","severity":{"version":"4.0","score":6.9,"vector":"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","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-11","score":0.00508,"percentile":0.43851,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-22"],"published":"2026-08-07T15:04:52Z","modified":"2026-10-28T02:30:44Z","fixes":[{"ecosystem":"Packagist","package":"smarty/smarty","fixed_in":["5.8.4"],"sources":["ghsa","osv"]}],"affected":[{"source":"ghsa","ecosystem":"Packagist","package":"smarty/smarty","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.0.0"},{"fixed":"5.8.4"}]}]},{"source":"osv","ecosystem":"Packagist","package":"smarty/smarty","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.0.0"},{"fixed":"5.8.4"}]}],"versions":["v5.0.0","v5.0.1","v5.0.2","v5.1.0","v5.2.0","v5.3.0","v5.3.1","v5.4.0","v5.4.1","v5.4.2","v5.4.3","v5.4.4","v5.4.5","v5.5.0","v5.5.1","v5.5.2","v5.6.0","v5.7.0","v5.8.0","v5.8.1","v5.8.2","v5.8.3"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"smarty3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.1.21-1","3.1.21-1ubuntu1","3.1.21-1ubuntu1+esm1","3.1.21-1ubuntu1+esm2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"smarty3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.1.31+20161214.1.c7d42e4+selfpack1-2","3.1.31+20161214.1.c7d42e4+selfpack1-3","3.1.31+20161214.1.c7d42e4+selfpack1-3ubuntu0.1","3.1.31+20161214.1.c7d42e4+selfpack1-3ubuntu0.1+esm1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"smarty3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.1.33+20180830.1.3a78a21f+selfpack1-1","3.1.34+20190228.1.c9f0de05+selfpack1-1","3.1.34+20190228.1.c9f0de05+selfpack1-1ubuntu0.1~esm1","3.1.34+20190228.1.c9f0de05+selfpack1-1ubuntu0.1","3.1.34+20190228.1.c9f0de05+selfpack1-1ubuntu0.1+esm1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"smarty3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.1.39-2","3.1.39-2ubuntu1","3.1.39-2ubuntu1.22.04.1","3.1.39-2ubuntu1.22.04.2"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"smarty3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.1.48-1","3.1.48-1ubuntu0.24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"smarty4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.3.1-1","4.3.1-1ubuntu0.24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:26.10","package":"smarty3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.1.48-2build1"]},{"source":"osv","ecosystem":"Ubuntu:26.10","package":"smarty4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.5.5-1"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"smarty3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.1.48-2","3.1.48-2build1"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"smarty4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.5.5-1"]}],"products":[{"vendor":"smarty-php","product":"smarty"}],"references":[{"url":"https://github.com/smarty-php/smarty/security/advisories/GHSA-rjhh-76wf-8xmw","tags":["x_refsource_CONFIRM","exploit","advisory","web","report"]},{"url":"https://github.com/smarty-php/smarty/pull/1195","tags":["x_refsource_MISC","fix","web","report"]},{"url":"https://github.com/smarty-php/smarty/commit/3c9f77a2e06ce319ae0092496af32cc8f3adc52e","tags":["x_refsource_MISC","fix","web","report"]},{"url":"https://github.com/smarty-php/smarty/releases/tag/v5.8.4","tags":["x_refsource_MISC","web","report"]},{"url":"https://github.com/advisories/GHSA-rjhh-76wf-8xmw"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/62xxx/CVE-2026-62996.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-62996","tags":["advisory"]},{"url":"https://github.com/smarty-php/smarty","tags":["package"]},{"url":"https://ubuntu.com/security/CVE-2026-62996","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-62996","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2026-62996","title":"Smarty Security stream restriction bypass through stream: resource","description":"Smarty is a template engine for PHP, facilitating the separation of presentation (HTML/CSS) from application logic. From 5.0.0 until 5.8.4, Smarty's stream: resource-name handling does not adequately restrict which PHP stream wrappers and filter chains can be referenced from a template, allowing a php://filter-wrapped resource name to be used to read the contents of arbitrary local files accessible to the PHP process. An attacker able to author or influence a template's resource reference could exploit this to disclose sensitive file contents outside the intended template/config scope. This issue is fixed in version 5.8.4.","status":"published","published":"2026-08-07T15:04:52.662Z","modified":"2026-08-07T17:08:09.71Z","cvss":[{"version":"4.0","score":6.9,"vector":"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","level":"medium","assessor":"cna"}],"cwes":["CWE-22"],"updated_at":"2026-11-02T14:20:14.999906Z"}],"euvd":[{"id":"EUVD-2026-54499","description":"Smarty is a template engine for PHP, facilitating the separation of presentation (HTML/CSS) from application logic. From 5.0.0 until 5.8.4, Smarty's stream: resource-name handling does not adequately restrict which PHP stream wrappers and filter chains can be referenced from a template, allowing a php://filter-wrapped resource name to be used to read the contents of arbitrary local files accessible to the PHP process. An attacker able to author or influence a template's resource reference could exploit this to disclose sensitive file contents outside the intended template/config scope. This issue is fixed in version 5.8.4.","status":"published","published":"2026-08-07T15:04:52Z","modified":"2026-08-07T17:08:09Z","cvss":[{"version":"4.0","score":6.9,"vector":"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","level":"medium"}],"updated_at":"2026-11-02T18:02:06.930016Z"}],"ghsa":[{"id":"GHSA-rjhh-76wf-8xmw","title":"Smarty Security stream restriction bypass through stream: resource","description":"`smarty/smarty` version `5.8.0` can read local files through PHP stream wrappers even when Smarty Security is enabled and all streams are disabled with `Security::$streams = null`.\n\nThe bypass uses Smarty's built-in `stream:` resource type. A template such as:\n\n```smarty\n{include file=\"stream:php://filter/read=convert.base64-encode/resource=/tmp/secret.tpl\"}\n```\n\nis handled as Smarty resource type `stream`, so the security check that would normally reject the underlying `php` wrapper is not applied. `StreamPlugin` then opens the nested `php://filter/...` URI directly.\n\nFor comparison, the direct resource:\n\n```smarty\n{include file=\"php://filter/read=convert.base64-encode/resource=/tmp/secret.tpl\"}\n```\n\nis blocked with `stream 'php' not allowed by security setting`.\n\nAffected package:\n\n- Ecosystem: Packagist / Composer\n- Package: `smarty/smarty`\n- Confirmed affected version: `5.8.0`\n- Confirmed source reference from Composer lock: `78d259d3b971c59a0cd719c270cc5cbb740c36a7`\n- Current stable version on Packagist at review time: `v5.8.0`\n- Packagist usage at review time: 41,113,855 total downloads and 840,604 monthly downloads\n\nRelevant code paths:\n\n- `Smarty\\Resource\\BasePlugin::load(...)`\n- `Smarty\\Resource\\StreamPlugin::getContent(...)`\n- `Smarty\\Security::isTrustedStream(...)`\n\n`BasePlugin::load()` maps the built-in resource name `stream` directly to `StreamPlugin` before the code path that checks PHP stream wrappers with `stream_get_wrappers()` and `Security::isTrustedStream($type)`. `StreamPlugin::getContent()` later calls `fopen($filepath, 'r+')` on the nested URI when the resource name contains `://`.\n\nPreconditions:\n\nAn application must render templates that are not fully trusted while relying on Smarty Security to restrict local files and PHP stream wrappers. The PoC sets:\n\n```php\n$smarty-\u003eenableSecurity();\n$smarty-\u003esecurity_policy-\u003estreams = null;\n```\n\nLocal reproduction:\n\nThe PoC creates a disposable template directory and a separate outside directory. It enables Smarty Security, disables all streams, and then compares three includes:\n\n1. `../outside/secret.tpl` to confirm the ordinary trusted-directory boundary is enforced.\n2. `php://filter/...` to confirm direct PHP streams are blocked by `Security::$streams = null`.\n3. `stream:php://filter/...` to show the built-in `stream:` resource bypasses the same restriction and reads the outside file.\n\nRun:\n\n```shell\nphp -d display_errors=1 poc.php\n```\n\nObserved sanitized output:\n\n```text\npackage=smarty/smarty\ninstalled_version=v5.8.0\ntemplate_dir=\u003ctmp\u003e/templates\noutside_template=\u003ctmp\u003e/outside/secret.tpl\nplain_dotdot_include=BLOCKED:Smarty\\Exception:Smarty Security: not trusted file path '\u003ctmp\u003e/outside/secret.tpl'\ndirect_php_filter_include=BLOCKED:Smarty\\Exception:stream 'php' not allowed by security setting\nstream_php_filter_include=OK:U01BUlRZX1NUUkVBTV9XUkFQUEVSX1NFQ1VSSVRZX0VTQ0FQRQ==\nexpected_base64=U01BUlRZX1NUUkVBTV9XUkFQUEVSX1NFQ1VSSVRZX0VTQ0FQRQ==\n```\n\nThe `plain_dotdot_include` line shows the directory boundary is enforced for ordinary traversal. The `direct_php_filter_include` line shows the same policy rejects `php://filter` when used directly. The `stream_php_filter_include` line shows that wrapping the same URI in Smarty's `stream:` resource bypasses that restriction and reads the outside file.\n\nImpact:\n\nA template author can bypass Smarty Security stream restrictions and read local files that are readable by the PHP process. With `php://filter`, file contents can be base64 encoded and rendered back through the template. This bypasses both the intended `Security::$streams = null` restriction and the normal trusted-template-directory check that blocks `../` traversal.\n\nDuplicate checks:\n\n- OSV query for `Packagist/smarty/smarty` version `5.8.0` returned no vulnerabilities.\n- GitHub advisory query for `ecosystem=composer` and `affects=smarty/smarty` returned historical Smarty advisories, including sandbox escapes, PHP code injection, XSS, and older path traversal issues. The listed path traversal advisories affect older versions and do not describe this current `stream:php://filter` resource-wrapper bypass in 5.8.0.\n- GitHub issue search in `smarty-php/smarty` for `stream:php://filter` returned zero results.\n- Public searches for `Smarty StreamPlugin php://filter` and `smarty/smarty isTrustedStream stream:` did not identify a clear public duplicate during triage.\n\nSuggested remediation:\n\nWhen resolving the built-in `stream:` resource, parse and validate the nested URI scheme before opening it. For example, `stream:php://filter/...` should call `Security::isTrustedStream('php')`, and `Security::$streams = null` should block the resource before `StreamPlugin::getContent()` reaches `fopen()`.\n\nIt would also be safer for `StreamPlugin` to reject nested stream wrappers by default unless the underlying wrapper is explicitly allowed by the active security policy.","status":"published","published":"2026-08-07T15:10:51Z","modified":"2026-08-07T15:10:53Z","cvss":[{"version":"4.0","score":6.9,"vector":"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","level":"medium"}],"cwes":["CWE-22"],"updated_at":"2026-11-02T14:40:57.999375Z"}],"nvd":[{"id":"CVE-2026-62996","description":"Smarty is a template engine for PHP, facilitating the separation of presentation (HTML/CSS) from application logic. From 5.0.0 until 5.8.4, Smarty's stream: resource-name handling does not adequately restrict which PHP stream wrappers and filter chains can be referenced from a template, allowing a php://filter-wrapped resource name to be used to read the contents of arbitrary local files accessible to the PHP process. An attacker able to author or influence a template's resource reference could exploit this to disclose sensitive file contents outside the intended template/config scope. This issue is fixed in version 5.8.4.","status":"published","published":"2026-08-07T16:17:26Z","modified":"2026-10-24T16:10:00.153Z","cvss":[{"version":"4.0","score":6.9,"vector":"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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"medium","assessor":"secondary"}],"cwes":["CWE-22"],"updated_at":"2026-11-02T14:12:35.386166Z"}],"osv":[{"id":"CVE-2026-62996","title":"Smarty Security stream restriction bypass through stream: resource","description":"Smarty is a template engine for PHP, facilitating the separation of presentation (HTML/CSS) from application logic. From 5.0.0 until 5.8.4, Smarty's stream: resource-name handling does not adequately restrict which PHP stream wrappers and filter chains can be referenced from a template, allowing a php://filter-wrapped resource name to be used to read the contents of arbitrary local files accessible to the PHP process. An attacker able to author or influence a template's resource reference could exploit this to disclose sensitive file contents outside the intended template/config scope. This issue is fixed in version 5.8.4.","status":"published","published":"2026-08-07T15:04:52.662Z","modified":"2026-10-28T02:30:44.892837247Z","cvss":[{"version":"4.0","score":6.9,"vector":"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","level":"medium"}],"cwes":["CWE-22"],"updated_at":"2026-11-02T15:45:13.306117Z"},{"id":"GHSA-rjhh-76wf-8xmw","title":"Smarty Security stream restriction bypass through stream: resource","description":"`smarty/smarty` version `5.8.0` can read local files through PHP stream wrappers even when Smarty Security is enabled and all streams are disabled with `Security::$streams = null`.\n\nThe bypass uses Smarty's built-in `stream:` resource type. A template such as:\n\n```smarty\n{include file=\"stream:php://filter/read=convert.base64-encode/resource=/tmp/secret.tpl\"}\n```\n\nis handled as Smarty resource type `stream`, so the security check that would normally reject the underlying `php` wrapper is not applied. `StreamPlugin` then opens the nested `php://filter/...` URI directly.\n\nFor comparison, the direct resource:\n\n```smarty\n{include file=\"php://filter/read=convert.base64-encode/resource=/tmp/secret.tpl\"}\n```\n\nis blocked with `stream 'php' not allowed by security setting`.\n\nAffected package:\n\n- Ecosystem: Packagist / Composer\n- Package: `smarty/smarty`\n- Confirmed affected version: `5.8.0`\n- Confirmed source reference from Composer lock: `78d259d3b971c59a0cd719c270cc5cbb740c36a7`\n- Current stable version on Packagist at review time: `v5.8.0`\n- Packagist usage at review time: 41,113,855 total downloads and 840,604 monthly downloads\n\nRelevant code paths:\n\n- `Smarty\\Resource\\BasePlugin::load(...)`\n- `Smarty\\Resource\\StreamPlugin::getContent(...)`\n- `Smarty\\Security::isTrustedStream(...)`\n\n`BasePlugin::load()` maps the built-in resource name `stream` directly to `StreamPlugin` before the code path that checks PHP stream wrappers with `stream_get_wrappers()` and `Security::isTrustedStream($type)`. `StreamPlugin::getContent()` later calls `fopen($filepath, 'r+')` on the nested URI when the resource name contains `://`.\n\nPreconditions:\n\nAn application must render templates that are not fully trusted while relying on Smarty Security to restrict local files and PHP stream wrappers. The PoC sets:\n\n```php\n$smarty-\u003eenableSecurity();\n$smarty-\u003esecurity_policy-\u003estreams = null;\n```\n\nLocal reproduction:\n\nThe PoC creates a disposable template directory and a separate outside directory. It enables Smarty Security, disables all streams, and then compares three includes:\n\n1. `../outside/secret.tpl` to confirm the ordinary trusted-directory boundary is enforced.\n2. `php://filter/...` to confirm direct PHP streams are blocked by `Security::$streams = null`.\n3. `stream:php://filter/...` to show the built-in `stream:` resource bypasses the same restriction and reads the outside file.\n\nRun:\n\n```shell\nphp -d display_errors=1 poc.php\n```\n\nObserved sanitized output:\n\n```text\npackage=smarty/smarty\ninstalled_version=v5.8.0\ntemplate_dir=\u003ctmp\u003e/templates\noutside_template=\u003ctmp\u003e/outside/secret.tpl\nplain_dotdot_include=BLOCKED:Smarty\\Exception:Smarty Security: not trusted file path '\u003ctmp\u003e/outside/secret.tpl'\ndirect_php_filter_include=BLOCKED:Smarty\\Exception:stream 'php' not allowed by security setting\nstream_php_filter_include=OK:U01BUlRZX1NUUkVBTV9XUkFQUEVSX1NFQ1VSSVRZX0VTQ0FQRQ==\nexpected_base64=U01BUlRZX1NUUkVBTV9XUkFQUEVSX1NFQ1VSSVRZX0VTQ0FQRQ==\n```\n\nThe `plain_dotdot_include` line shows the directory boundary is enforced for ordinary traversal. The `direct_php_filter_include` line shows the same policy rejects `php://filter` when used directly. The `stream_php_filter_include` line shows that wrapping the same URI in Smarty's `stream:` resource bypasses that restriction and reads the outside file.\n\nImpact:\n\nA template author can bypass Smarty Security stream restrictions and read local files that are readable by the PHP process. With `php://filter`, file contents can be base64 encoded and rendered back through the template. This bypasses both the intended `Security::$streams = null` restriction and the normal trusted-template-directory check that blocks `../` traversal.\n\nDuplicate checks:\n\n- OSV query for `Packagist/smarty/smarty` version `5.8.0` returned no vulnerabilities.\n- GitHub advisory query for `ecosystem=composer` and `affects=smarty/smarty` returned historical Smarty advisories, including sandbox escapes, PHP code injection, XSS, and older path traversal issues. The listed path traversal advisories affect older versions and do not describe this current `stream:php://filter` resource-wrapper bypass in 5.8.0.\n- GitHub issue search in `smarty-php/smarty` for `stream:php://filter` returned zero results.\n- Public searches for `Smarty StreamPlugin php://filter` and `smarty/smarty isTrustedStream stream:` did not identify a clear public duplicate during triage.\n\nSuggested remediation:\n\nWhen resolving the built-in `stream:` resource, parse and validate the nested URI scheme before opening it. For example, `stream:php://filter/...` should call `Security::isTrustedStream('php')`, and `Security::$streams = null` should block the resource before `StreamPlugin::getContent()` reaches `fopen()`.\n\nIt would also be safer for `StreamPlugin` to reject nested stream wrappers by default unless the underlying wrapper is explicitly allowed by the active security policy.","status":"published","published":"2026-08-07T15:10:51Z","modified":"2026-08-07T15:25:57.197918Z","cvss":[{"version":"4.0","score":6.9,"vector":"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","level":"medium"}],"cwes":["CWE-22"],"updated_at":"2026-11-02T15:46:55.877614Z"},{"id":"UBUNTU-CVE-2026-62996","description":"Smarty is a template engine for PHP, facilitating the separation of presentation (HTML/CSS) from application logic. From 5.0.0 until 5.8.4, Smarty's stream: resource-name handling does not adequately restrict which PHP stream wrappers and filter chains can be referenced from a template, allowing a php://filter-wrapped resource name to be used to read the contents of arbitrary local files accessible to the PHP process. An attacker able to author or influence a template's resource reference could exploit this to disclose sensitive file contents outside the intended template/config scope. This issue is fixed in version 5.8.4.","status":"published","published":"2026-08-07T16:17:00Z","modified":"2026-10-17T13:00:30.877473532Z","cvss":[{"version":"4.0","score":6.9,"vector":"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","level":"medium"}],"updated_at":"2026-11-02T16:56:43.630667Z"}]}}