AI Science Tracker

Smarty before 4.5.8 and 5.x before 5.8.5 PHP Code Injection via extends: Inheritance Cache

smarty · AI involvement attributed to AISLE AI-native discovery engine (specific model not identified)

Finding and attribution

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.

Product: smarty. AI system: AISLE AI-native discovery engine (specific model not identified). Team / organization: AISLE (self-attributed AI-engine discovery); VulnCheck CNA record.

CVE identifiers: CVE-2026-82531.

AI and human contribution (source account): The primary AISLE CVE-discoveries index explicitly scopes its listed cases as CVEs discovered by its AI-native engine and individually lists CVE-2026-82531. This is AISLE's self-attributed case-specific AI-engine claim. The available sources do not identify a model, establish autonomy or first-discovery priority, or define the human/tool work split.

Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.

Discovery context: The CNA record gives the public CVE publication date. The checked sources do not establish exploitation in the wild or zero-day status.

Remediation status: fix documented. CNA version statements: smarty: 0 < 4.5.8 affected; 5.0.0 < 5.8.5 affected; 4.5.8 unaffected; 5.8.5 unaffected. CNA references a patch: https://github.com/smarty-php/smarty/commit/c0fdd4824aca4f67e814b50703cfee1dfde41414.

A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.

Disclosed 6 Oct 2026. AI attribution date not established by the source. Sources checked 17 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: Critical · highest recorded score 9.2. Documented technical effects: code execution.

Severity, consequences and exploitation evidence

Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.

  • CVE-2026-82531: CVSS 4.0 · 9.2 (Critical) · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N. CVE Program CNA record · checked 17 Nov 2026.
  • CVE-2026-82531: CVSS 3.1 · 8.1 (High) · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. CVE Program CNA record · checked 17 Nov 2026.

CVE-2026-82531: code execution.
Prerequisites / affected scope: smarty: 0 < 4.5.8 affected; 5.0.0 < 5.8.5 affected; 4.5.8 unaffected; 5.8.5 unaffected.
Exploitation evidence: The CNA description establishes the stated technical effect. The checked CNA record does not report exploitation in the wild; no exploitability beyond the description is inferred.. Impact source · checked 17 Nov 2026.

Documented fix: CNA version statements: smarty: 0 < 4.5.8 affected; 5.0.0 < 5.8.5 affected; 4.5.8 unaffected; 5.8.5 unaffected. CNA references a patch: https://github.com/smarty-php/smarty/commit/c0fdd4824aca4f67e814b50703cfee1dfde41414.

Original evidence

Download this source record (JSON)

Open this case in the interactive tracker · Browse all static security cases