Bug 2526557 (CVE-2026-62993) - CVE-2026-62993 smarty-php/smarty: Smarty: Server-Side Request Forgery via redirect bypass in {fetch} handling
Summary: CVE-2026-62993 smarty-php/smarty: Smarty: Server-Side Request Forgery via red...
Keywords:
Status: NEW
Alias: CVE-2026-62993
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2540933 2540934 2540935 2540936
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-08-31 21:11 UTC by OSIDB Bzimport
Modified: 2026-09-25 05:09 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-08-31 21:11:27 UTC
Smarty is a template engine for PHP, facilitating the separation of presentation (HTML/CSS) from application logic. Prior to 4.5.7 and 5.8.2, depending on the release line, Smarty's {fetch} handling in libs/plugins/function.fetch.php and src/FunctionHandler/Fetch.php used Security::isTrustedUri() to validate only the initial remote URL against trusted_uri when a security policy was active. For resources handled by file_get_contents(), including HTTPS URLs, PHP followed HTTP redirects by default. An attacker who could supply or influence a fetch target and had an open redirect on a trusted host could redirect the request to an attacker-chosen internal endpoint, bypass the trusted_uri allowlist, and perform server-side request forgery. This issue is fixed in versions 4.5.7 and 5.8.2.


Note You need to log in before you can comment on or make changes to this bug.