Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.9amended

Smarty: Symlink path traversal out of trusted directories

CVE-2026-62992GHSA-f6wf-28g6-769x

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (smarty/smarty 5.8.2, 4.5.7), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Packagist smarty/smarty

    Affected
    >= 5.0.0, < 5.8.2< 4.5.7
    Fixed in
    5.8.2, 4.5.7

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
6.9 · 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 · score source
EPSS
  • CVE-2026-62992: 0.53% estimated exploitation activity in the next 30 days; percentile 45.08 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

When Smarty's Security policy is enabled, securedir (and the configured template/trusted directories) restrict which local files a template may read via {include} and {fetch}. The trust check in Security::checkDir() resolved the requested path with Smarty::realpath(), which normalizes the path as a string only and does not follow symbolic links. A symlink placed inside a trusted directory therefore passed the trust check, while the underlying filegetcontents() followed it to an arbitrary file outside the sandbox (e.g. /etc/passwd). Impact An attacker able to (a) cause a symlink to exist inside a trusted directory (e.g. a user-upload area located within the template path) and (b) cause a template to reference that path can read arbitrary files readable by the PHP process, escaping the securedir boundary. Confidentiality impact only. Patches Fixed in 5.8.2. Security::checkDir() now resolves the requested file with native realpath() and re-validates the canonical, symlink-free path…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-f6wf-28g6-769x

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-f6wf-28g6-769x

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-62992

Advisory: Smarty: Symlink path traversal out of trusted directories
IDs: CVE-2026-62992, GHSA-f6wf-28g6-769x
Record: https://patchnext.com/advisories/cve-2026-62992 (revision 3, source checked 26 Oct 2026, 14:50 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: smarty/smarty 5.8.2, 4.5.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist smarty/smarty: affected >= 5.0.0, < 5.8.2; < 4.5.7; fixed in 5.8.2, 4.5.7

## Suggested inspection (read-only)
- Packagist smarty/smarty: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on smarty/smarty.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-f6wf-28g6-769x (OSV record GHSA-f6wf-28g6-769x lists affected ranges: Packagist smarty/smarty >=5.0.0 =0 <4.5.7 (fixed))
- Verified: https://github.com/advisories/GHSA-f6wf-28g6-769x (GitHub-reviewed advisory GHSA-f6wf-28g6-769x lists affected ranges: Packagist smarty/smarty >=5.0.0 =0 <4.5.7)

Commands are suggestions: review each one before running it.

Loading voting…