CVE-2026-62993: Smarty: SSRF via redirect bypass of trusted_uri using {fetch}
When a Security policy is active, {fetch} validates the requested remote URL against the trusteduri allowlist via Security::isTrustedUri(). For non-http:// schemes (e.g. https://) the resource was then read with filegetcontents(), which follows HTTP redirects by default.
Published Sep 1, 2026
Affected packages
smarty/smarty
- Ecosystem
- Composer (PHP)
- Affected
- >= 5.0.0, < 5.8.2
- Fixed in
- 5.8.2
- Check
composer show smarty/smarty
smarty/smarty
- Ecosystem
- Composer (PHP)
- Affected
- < 4.5.7
- Fixed in
- 4.5.7
- Check
composer show smarty/smarty
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
When a Security policy is active, {fetch} validates the requested remote URL against the trusted_uri allowlist via Security::isTrustedUri(). For non-http:// schemes (e.g. https://) the resource was then read with file_get_contents(), which follows HTTP redirects by default. Because isTrustedUri() only validates the initial URL, an open redirect on an otherwise-trusted host could be used to redirect the request to a non-trusted, internal target — bypassing the trusted_uri policy.
Impact
An attacker who can supply a fetch target (or influence one) and who has an open redirect available on a trusted host can cause the server to issue requests to attacker-chosen internal endpoints, defeating the trusted_uri allowlist (server-side request forgery).
Patches
Fixed in 5.8.2. When a security policy is active, {fetch} now passes a stream context that disables redirect following (follow_location => 0, max_redirects => 1) to file_get_contents() for remote resources. Behavior is unchanged when no security policy is set, since there is no trusted_uri to bypass.
Workarounds
Avoid fetching remote resources from within templates under untrusted control; ensure hosts listed in trusted_uri do not expose open redirects.
References
- https://github.com/smarty-php/smarty/security/advisories/GHSA-cq55-c7wv-pxmq
- https://nvd.nist.gov/vuln/detail/CVE-2026-62993
- https://github.com/smarty-php/smarty/pull/1194
- https://github.com/smarty-php/smarty/commit/31e06fc087a8b5a9b236c1e5dacc1c2850a2c115
- https://github.com/smarty-php/smarty/commit/a1ccdb0518021a559b4066c37b76a42c86bbce90
- https://github.com/smarty-php/smarty/releases/tag/v4.5.7
- https://github.com/smarty-php/smarty/releases/tag/v5.8.2
- https://github.com/advisories/GHSA-cq55-c7wv-pxmq
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-62992
Smarty: Symlink path traversal out of trusted directories
medium6.9Aug 7, 2026CVE-2026-62996
Smarty Security stream restriction bypass through stream: resource
medium6.9Aug 7, 2026CVE-2024-35226
Smarty vulnerable to PHP Code Injection by malicious attribute in extends-tag
high7.3May 29, 2024
