Smarty before 3.1.39 allows code injection via an unexpected function name after a {function name= substring.
CVE-2021-26120
This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 82.3%, top 0% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High exploitation likelihood — EPSS 82%
A fix is available — apply it.
- CVSS v3
- 9.8
- EG Score
- 9.8(medium)
- EG Risk
- 82(Track*)EG Risk 82/100SSVC: Track*
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity98% × 45%Exploitation82% × 40%Automatability30% × 15%Action: Watch closely — could escalate to Attend. - EPSS
- 99.6%
- KEV
- Not listed
Published
February 22, 2021
Last Modified
November 21, 2024
Advisory Details (5)
Auto-updated Jun 22, 2026Smarty: Multiple vulnerabilities (GLSA 202105-06) — Gentoo security
https://security.gentoo.org/glsa/202105-06[SECURITY] [DLA 2618-2] smarty3 regression update
https://lists.debian.org/debian-lts-announce/2021/04/msg00014.html[SECURITY] [DLA 2618-1] smarty3 security update
https://lists.debian.org/debian-lts-announce/2021/04/msg00004.htmlsmarty/CHANGELOG.md at master · smarty-php/smarty · GitHub
https://github.com/smarty-php/smarty/blob/master/CHANGELOG.mdPatch Availability(3)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | smarty3 (3.1.31+20161214.1.c7d42e4+selfpack1-3ubuntu0.1) @ bionic | 2026-05-26 | ubuntu |
| ubuntu | smarty3 (3.1.21-1ubuntu1+esm1) @ xenial | 2026-05-26 | ubuntu |
| ubuntu | smarty3 (3.1.34+20190228.1.c9f0de05+selfpack1-1ubuntu0.1~esm1) @ focal | 2026-05-26 | ubuntu |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
Packagist(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| smarty/smarty | v2.6.24 ... v3.1.38 (37 versions) | 3.1.39 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(3)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 9× in last 7d / 23× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-24 14:15 UTCEPSS rescore
- 2026-07-23 01:58 UTCEG score recompute
- 2026-07-22 22:45 UTCEG score recompute
- 2026-07-22 14:06 UTCEPSS rescore
- 2026-07-22 14:06 UTCEPSS rescore
- 2026-07-21 15:22 UTCEPSS rescore
- 2026-07-21 15:22 UTCEPSS rescore
- 2026-07-20 17:05 UTCEPSS rescore
- 2026-07-19 01:29 UTCOSV refresh
- 2026-07-15 16:55 UTCEPSS rescore
- 2026-07-15 16:55 UTCEPSS rescore
- 2026-07-15 01:58 UTCEPSS rescore
- 2026-07-11 08:25 UTCEPSS rescore
- 2026-07-11 08:25 UTCEPSS rescore
- 2026-07-08 15:12 UTCEPSS rescore
- 2026-07-04 06:29 UTCEPSS rescore
- 2026-07-04 06:29 UTCEPSS rescore
- 2026-07-01 15:03 UTCEPSS rescore
- 2026-07-01 08:18 UTCOSV refresh
- 2026-06-28 04:54 UTCEPSS rescore
- 2026-06-28 04:54 UTCEPSS rescore
- 2026-06-25 13:48 UTCEPSS rescore
- 2026-06-25 13:48 UTCEPSS rescore
- 2026-06-23 21:31 UTCEPSS rescore
- 2026-06-23 21:31 UTCEPSS rescore
Show 37 moreShow fewer
- 2026-06-21 14:55 UTCEPSS rescore
- 2026-06-21 14:54 UTCEPSS rescore
- 2026-06-21 01:58 UTCEPSS rescore
- 2026-06-21 01:58 UTCEPSS rescore
- 2026-06-16 17:51 UTCEPSS rescore
- 2026-06-15 17:46 UTCEPSS rescore
- 2026-06-14 23:15 UTCEPSS rescore
- 2026-06-13 22:58 UTCEPSS rescore
- 2026-06-13 22:58 UTCEPSS rescore
- 2026-06-13 13:13 UTCOSV refresh
- 2026-06-12 23:10 UTCEPSS rescore
- 2026-06-11 13:58 UTCEPSS rescore
- 2026-06-10 22:16 UTCEPSS rescore
- 2026-06-10 13:20 UTCEPSS rescore
- 2026-06-08 14:15 UTCEPSS rescore
- 2026-06-07 15:23 UTCEPSS rescore
- 2026-06-07 15:23 UTCEPSS rescore
- 2026-06-06 13:46 UTCEPSS rescore
- 2026-06-06 13:46 UTCEPSS rescore
- 2026-06-06 13:46 UTCEPSS rescore
- 2026-06-05 22:45 UTCEPSS rescore
- 2026-06-05 22:45 UTCEPSS rescore
- 2026-06-05 06:09 UTCEPSS rescore
- 2026-06-05 06:09 UTCEPSS rescore
- 2026-06-02 20:11 UTCEPSS rescore
- 2026-06-02 20:11 UTCEPSS rescore
- 2026-06-02 20:11 UTCEPSS rescore
- 2026-06-01 13:50 UTCEPSS rescore
- 2026-06-01 13:50 UTCEPSS rescore
- 2026-05-31 00:15 UTCEPSS rescore
- 2026-05-29 13:42 UTCEPSS rescore
- 2026-05-28 13:43 UTCEPSS rescore
- 2026-05-28 13:43 UTCEPSS rescore
- 2026-05-26 20:36 UTCEG score recompute
- 2026-05-26 20:36 UTCVendor advisory
- 2026-05-26 07:17 UTCEPSS rescore
- 2026-05-26 07:17 UTCEPSS rescore
Related CVEs(same vendor + same CWE)
Same vendor
10 shownubuntu
Same CWE
10 shownCWE-94
Frequently asked(5)
What is CVE-2021-26120?
When was CVE-2021-26120 disclosed?
Is CVE-2021-26120 actively exploited?
What is the CVSS score of CVE-2021-26120?
How do I remediate CVE-2021-26120?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2021-26120
Is Your Infrastructure Affected by CVE-2021-26120?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.