Smarty: SSRF via redirect bypass of trusted_uri using {fetch}

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

• CISA KEV Not listed.
• EPSS 0.0057, the 47th percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

1. 31 Oct 2026, 14:06 UTC First seen by agentprime
2. 31 Oct 2026, 14:06 UTC Confirmed by OSV

Sources

• GitHub Advisory Database: GHSA-cq55-c7wv-pxmq
• OSV: GHSA-cq55-c7wv-pxmq
• github.com/smarty-php/smarty/security/advisories/GHSA-cq55-c7wv-pxmq
• nvd.nist.gov/vuln/detail/CVE-2026-62993
• github.com/smarty-php/smarty/pull/1194
• github.com/smarty-php/smarty/commit/31e06fc087a8b5a9b236c1e5dacc1c2850a2c115
• github.com/smarty-php/smarty/commit/a1ccdb0518021a559b4066c37b76a42c86bbce90
• github.com/smarty-php/smarty
• github.com/smarty-php/smarty/releases/tag/v4.5.7
• github.com/smarty-php/smarty/releases/tag/v5.8.2

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.