cve.bz

CVE-2026-62992 smarty-php smarty: Path traversal

6.9 mediumEPSS 0.5%Fix available

Medium (6.9) in smarty-php smarty. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in smarty/smarty 4.5.7, 5.8.2.

On this page
Smarty is a template engine for PHP, facilitating the separation of presentation (HTML/CSS) from application logic. Prior to 5.8.2 (and 4.5.7 on the 4.x line), Security::_checkDir() does not fully resolve symbolic links before validating that a requested path lies within a configured secure directory. An attacker able to place or reference a symlink within a directory Smarty treats as trusted (e.g., a template or config directory) could use it to point outside the intended secure directory, bypassing the containment check and reading arbitrary files accessible to the PHP process. This issue is fixed in versions 5.8.2 and 4.5.7.

Severity

CVSS 4.0

6.9 medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 46th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-08-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
CWE-61 UNIX Symbolic Link (Symlink) Following
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-62992 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-62992?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-62992?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-62992 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
smarty-php smarty>= 5.0.0, < 5.8.2
smarty-php smarty< 4.5.7

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-f6wf-28g6-769xPackagistsmarty/smarty>=5.0.0 <5.8.25.8.2
GHSA-f6wf-28g6-769xPackagistsmarty/smarty<4.5.74.5.7

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13smarty3, smarty4no fix listedDEBIAN-CVE-2026-62992
Debian14smarty3no fix listedDEBIAN-CVE-2026-62992
Debian14smarty44.5.8-1DEBIAN-CVE-2026-62992
Ubuntu22.04:LTS, Pro:16.04:LTS, Pro:18.04:LTS and 1 moresmarty3no fix listedUBUNTU-CVE-2026-62992
Ubuntu24.04:LTS, 26.04:LTS, 26.10smarty3, smarty4no fix listedUBUNTU-CVE-2026-62992

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Attack patterns (CAPEC)

  • CAPEC-27 Leveraging Race Conditions via Symbolic Links Likelihood: Medium · Severity: High
  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON