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 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.
References
- github.com/advisories/GHSA-cq55-c7wv-pxmq
- github.com/smarty-php/smarty/commit/31e06fc087a8b5a9b236c1e5dacc1c2850a2c115
- github.com/smarty-php/smarty/commit/a1ccdb0518021a559b4066c37b76a42c86bbce90
- github.com/smarty-php/smarty/pull/1194
- github.com/smarty-php/smarty/releases/tag/v4.5.7
- github.com/smarty-php/smarty/releases/tag/v5.8.2
- github.com/smarty-php/smarty/security/advisories/GHSA-cq55-c7wv-pxmq
- nvd.nist.gov/vuln/detail/CVE-2026-62993
Code Behaviors & Features
Detect and mitigate CVE-2026-62993 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →