CVE-2021-26119

Smarty before 3.1.39 allows a Sandbox Escape because $smarty.template_object can be accessed in sandbox mode.

Published: 2021-02-21 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2021-26119 is rated Moderate Risk (58.2/100): CVSS High severity, with high exploitation likelihood (EPSS 9.44%, 95th percentile). EPSS ranks this CVE among the most likely to be exploited in the near term. High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2021-26119

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 62.61% 9.44% -53.18%
2 2025-11-21 69.22% 62.61% -6.61%
3 2025-11-18 — 69.22% —

Full EPSS history (21 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2021-26119

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 [email protected]
5.0 2.0 MEDIUM
AV:N/AC:L/Au:N/C:N/I:P/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:N)
No availability impact.
 10.0 2.9 [email protected]

Weakness enumeration for CVE-2021-26119

GitHub Security Advisory for CVE-2021-26119

GHSA-w5hr-jm4j-9jvq · Severity: high · Ecosystem: composer — Sandbox escape through template_object in smarty

OS Trackers for CVE-2021-26119

vendor priority summary link
debian not yet assigned CVE-2021-26119 not yet assigned priority: Debian including 1 source packages (smarty3), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2021-26119
gentoo normal CVE-2021-26119: 1 GLSA(s) (202105-06), 1 atom(s) (dev-php/smarty); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2021-26119
ubuntu medium CVE-2021-26119 medium priority: Ubuntu including 1 source packages (smarty3), 15 status rows across 15 suites (bionic, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, trusty, upstream, xenial): not-affected 8, released 4, ignored 2, DNE 1. https://ubuntu.com/security/CVE-2021-26119

Affected software / configurations for CVE-2021-26119

Vendor Product Version Raw CPE
smarty smarty < 3.1.39 cpe:2.3:a:smarty:smarty:*:*:*:*:*:*:*:*
debian debian_linux 9.0 cpe:2.3:o:debian:debian_linux:9.0:*:*:*:*:*:*:*
debian debian_linux 10.0 cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*
debian debian_linux 11.0 cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*

References for CVE-2021-26119

cvelogic Threat Intelligence