# Smarty: Symlink path traversal out of trusted directories

Advisory record · `GHSA-f6wf-28g6-769x`

- **Identifiers:** `GHSA-f6wf-28g6-769x` · `CVE-2026-62992` · `PKSA-zw1q-6h4d-mf1m`
- **State:** Confirmed
- **Severity:** CVSS 6.9 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html) · [CWE-61](https://cwe.mitre.org/data/definitions/61.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md) · [CWE-61](https://agentprime.io/advisories/tag/cwe-61.md)
- **Published:** 7 Aug 2026
- **Updated:** 7 Aug 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 7 Aug 2026, 15:02 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `smarty/smarty` (Packagist): affected `>=5.0.0, <5.8.2 || <4.5.7`; fixed in `5.8.2`, `4.5.7`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Smarty versions below 4.5.7, and from 5.0.0 up to but not including 5.8.2, are vulnerable when the Security policy is enabled. A symlink inside a trusted directory can pass the path check, letting a template read arbitrary files outside the secure directory. An attacker would need to create such a symlink and get a template to reference it, and could then read files the PHP process can access. Upgrade to 4.5.7 or 5.8.2. Workaround: prevent untrusted users from creating symlinks in trusted template directories.

Written 3 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.9 Medium, CVSS 4.0: `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`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0053, the 45th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:24 UTC: First seen by agentprime
- 31 Oct 2026, 14:24 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-f6wf-28g6-769x)

## Sources

- [GitHub Advisory Database: GHSA-f6wf-28g6-769x](https://github.com/advisories/GHSA-f6wf-28g6-769x)
- [OSV: GHSA-f6wf-28g6-769x](https://osv.dev/vulnerability/GHSA-f6wf-28g6-769x)
- <https://github.com/smarty-php/smarty/security/advisories/GHSA-f6wf-28g6-769x>
- <https://github.com/smarty-php/smarty/commit/99c048ce7a590c519b79fbd38ad0143a08183a1f>
- <https://github.com/smarty-php/smarty/commit/a1ccdb0518021a559b4066c37b76a42c86bbce90>
- <https://github.com/smarty-php/smarty>
- <https://github.com/smarty-php/smarty/releases/tag/v4.5.7>
- <https://github.com/smarty-php/smarty/releases/tag/v5.8.2>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-f6wf-28g6-769x>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-f6wf-28g6-769x/>. Everything for agents: <https://agentprime.io/llms.txt>.