Smarty before 4.5.8 and 5.x before 5.8.5 contains a code injection vulnerability where the top-level nocache_hash is never restored during extends:/multi-component template inheritance, leaving it null. Attackers can supply assigned data containing a forged SmartyNocache marker that is copied verbatim into the regenerated PHP cache file, executing arbitrary PHP on include for remote code execution.
CVE-2026-82531
HIGHPre-NVD 8.18.1ElevatedEG-KEV Tier 3: ElevatedEG-KEV is EchelonGraph's own tiering of exploitation signals from CISA KEV, CISA's SSVC data (Vulnrichment), ransomware data, public exploit-code references and EPSS.Tier 3 is not evidence of exploitation. It means public exploit code is referenced, or CISA's SSVC data says "public PoC", or EPSS ranks the CVE in the top 5%.Signals for this CVE: CISA's SSVC exploitation value: public PoC, other public exploit code (a GitHub or vendor proof of concept, or an Exploit-DB entry not marked verified).First public exploit code on record: 2026-10-07 (GitHub PoC murrez/CVE-2026-82531)EchelonGraph confidence 42%: a heuristic from the tier and the number of signals, not a measured probability.
EchelonGraph scoreMEDIUM confidence
“—” beside the score: it is equal to the CVSS score beside it.
This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.8% (57th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Also known asEUVD-2026-93376 (ENISA EUVD)Source: ENISA EUVD
8.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
- Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 8.1Exploit: Public PoCExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 8.1
- EG Score
- 8.1HIGHmedium confidence
- EG Risk
- 52EG Risk 52/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity81% × 45%Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.8%
- EPSS %ILE
- 57th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.
- EG Severity
- 8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
- EG Likelihood
- 0.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 6, 2026
Last Modified
October 6, 2026
Advisory Details (6)
Auto-updated Oct 6, 2026Patch available. Sources: github, github_commit, github_release.
Web page
Smarty before 4.5.8 and 5.x before 5.8.5 PHP Code Injection via extends: Inheritance Cache | Advisories | VulnCheck
https://www.vulncheck.com/advisories/smarty-before-4.5.8-and-5-x-before-5.8.5-php-code-injection-via-extends-inheritance-cacheGitHub release Patch Available
v4.5.8
Patch available: smarty-php/smarty v4.5.8
https://github.com/smarty-php/smarty/releases/tag/v4.5.8GitHub release Patch Available
v5.8.5
Patch available: smarty-php/smarty v5.8.5
https://github.com/smarty-php/smarty/releases/tag/v5.8.5GitHub commit Patch Available
commit 1cba51cb8135 (smarty-php/smarty)
Patch available: smarty-php/smarty v4.5.8 (contains commit 1cba51cb8135)
https://github.com/smarty-php/smarty/commit/1cba51cb813563eb61d963c83d28cd59f26b858dGitHub commit Patch Available
commit c0fdd4824aca (smarty-php/smarty)
Patch available: smarty-php/smarty v5.8.5 (contains commit c0fdd4824aca)
https://github.com/smarty-php/smarty/commit/c0fdd4824aca4f67e814b50703cfee1dfde41414GitHub advisoryMentions a patch (unverified)
Missing nocache-hash restoration lets assigned data inject executable PHP into regenerated cache files · Advisory · smarty-php/smarty · GitHub
https://github.com/smarty-php/smarty/security/advisories/GHSA-3w63-v7pm-cq9xAffected Packages
(6 across 3 ecosystems)
Debian:12(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| smarty3 | 3.1.47-2, 3.1.47-2+deb12u1, 3.1.48-1, 3.1.48-2 |
| — |
| smarty4 | 4.3.0-1 ... 4.5.5-1 (6 versions) |
| — |
Debian:13(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| smarty3 | 3.1.48-2 |
| — |
| smarty4 | 4.5.5-1 |
| — |
Debian:14(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| smarty3 | 3.1.48-2 |
| — |
| smarty4 | 4.5.5-1 |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 44× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.8% · 57th percentile
- 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.8% · 57th percentile
- 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.8% · 57th percentile
- 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.8% · 57th percentile
- 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.8% · 57th percentile
- 2026-10-27 21:10 UTCEG score recompute
- 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.8% · 57th percentile
- 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.8% · 57th percentile
- 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.8% · 57th percentile
- 2026-10-25 13:58 UTCEG score recompute
- 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.8% · 56th percentile
- 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.8% · 56th percentile
- 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.8% · 56th percentile
- 2026-10-22 11:37 UTCEG score recompute
- 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.8% · 56th percentile
- 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.8% · 56th percentile
- 2026-10-20 07:45 UTCEG score recompute
- 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.8% · 56th percentile
- 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.8% · 56th percentile
- 2026-10-18 03:08 UTCEG score recompute
- 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.8% · 56th percentile
- 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.8% · 56th percentile
- 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.8% · 56th percentile
- 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.8% · 56th percentile
- 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.8% · 56th percentile
Show 19 moreShow fewer
- 2026-10-13 06:03 UTCEG score recompute
- 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.8% · 56th percentile
- 2026-10-12 14:55 UTCEG score recompute
- 2026-10-11 19:19 UTCEG score recompute
- 2026-10-11 16:36 UTCEG score recompute
- 2026-10-11 13:54 UTCEG score recompute
- 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.8% · 56th percentile
- 2026-10-11 03:08 UTCEG score recompute
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.8% · 56th percentile
- 2026-10-10 15:13 UTCEG score recompute
- 2026-10-10 03:22 UTCEG score recompute
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.8% · 56th percentile
- 2026-10-09 03:40 UTCEG score recompute
- 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.8% · 55th percentile
- 2026-10-08 03:53 UTCEG score recompute
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.8% · 55th percentile
- 2026-10-06 13:29 UTCEG score recompute
- 2026-10-06 12:35 UTCEG score recomputeFirst assessed: 8.1 HIGH
- 2026-10-06 12:34 UTCMITRE cvelistV5first tracked
Publicly available exploits
(1 reference)Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.
- GitHub PoCmurrez/CVE-2026-82531Published Oct 7, 2026
Smarty is vulnerable to code injection through template inheritance. Crafted assigned data can inject a forged SmartyNocache marker into regenerated PHP cache files, potentially allowing attackers to execute arbitrary PHP code. The issue affects Smarty 4.5.7 and earlier, and 5.8.4 and earlier.
Open source ↗
Related CVEs(same product + same CWE)
Same product
10 shownDebian:12:smarty4 · Debian:12:smarty3
Frequently asked(5)
What is CVE-2026-82531?
CVE-2026-82531 is a high-severity vulnerability; its CVE record was published on October 6, 2026. Smarty before 4.5.8 and 5.x before 5.8.5 contains a code injection vulnerability where the top-level nocache_hash is never restored during extends:/multi-component template inheritance, leaving it null. Attackers can supply assigned data containing a forged SmartyNocache marker that is copied…
When was CVE-2026-82531 made public?
CVE-2026-82531 was made public on October 4, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on October 6, 2026. EchelonGraph's copy of the record carries a last-modified date of October 6, 2026; the record at its source may have been updated since.
Is CVE-2026-82531 actively exploited?
CVE-2026-82531 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (57th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-82531?
CVE-2026-82531 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-82531?
A fix for CVE-2026-82531 is available: update to the fixed version the vendor names in its advisory.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-82531
Is Your Infrastructure Affected by CVE-2026-82531?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.