One smarty3 issue fixed a long time ago in 3.0.7 upstream

Actually since this is bascially a non-issue and never got a either a
CVE nor a Debian BTS reference we might have removed it completely.
Since bugix tracking clear now kept it as alternative choice.