{"answers":{"affected":"4 open source packages ship an affected version, including smarty/smarty.","exploited":"There is no known exploitation of CVE-2026-62992 in the wild and no public exploit code.","fix":"Upgrade smarty/smarty to a fixed version for your release line: 4.5.7 or 5.8.2.","what":"CVE-2026-62992 is a medium-severity path traversal vulnerability in smarty-php smarty, published on 7 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-62992 and fix it if it is affected.\n\nWhat it is: CVE-2026-62992 is a medium-severity path traversal vulnerability in smarty-php smarty, published on 7 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-62992 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- smarty/smarty (Packagist): affected all versions; fixed in 4.5.7\n- smarty/smarty (Packagist): affected all versions; fixed in 4.5.7\n- smarty/smarty (Packagist): affected from 5.0.0; fixed in 5.8.2\n- smarty/smarty (Packagist): affected from 5.0.0; fixed in 5.8.2\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-62992/ (Markdown: https://insights.sbomify.com/CVE-2026-62992/index.md)","id":"CVE-2026-62992","markdown":"https://insights.sbomify.com/CVE-2026-62992/index.md","name":"CVE-2026-62992","record":{"aliases":["DEBIAN-CVE-2026-62992","GHSA-f6wf-28g6-769x","UBUNTU-CVE-2026-62992"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"PHP template engine","requires_auth":"high_privilege","summary":"An attacker can use symbolic links to bypass directory restrictions and read arbitrary files accessible to the PHP process.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-61","name":"UNIX Symbolic Link (Symlink) Following"},{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"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.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Smarty: Symlink path traversal out of trusted directories","id":"CVE-2026-62992","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":4,"n_references":5,"next":{"headline":"Smarty: SSRF via redirect bypass of trusted_uri using {fetch}","id":"CVE-2026-62993"},"packages":[{"ecosystem":"Packagist","fixed":["4.5.7"],"introduced":["0"],"last_affected":[],"package":"smarty/smarty","purl":null,"source":"GHSA-f6wf-28g6-769x"},{"ecosystem":"Packagist","fixed":["4.5.7"],"introduced":["0"],"last_affected":[],"package":"smarty/smarty","purl":"pkg:composer/smarty/smarty","source":"GHSA-f6wf-28g6-769x"},{"ecosystem":"Packagist","fixed":["5.8.2"],"introduced":["5.0.0"],"last_affected":[],"package":"smarty/smarty","purl":null,"source":"GHSA-f6wf-28g6-769x"},{"ecosystem":"Packagist","fixed":["5.8.2"],"introduced":["5.0.0"],"last_affected":[],"package":"smarty/smarty","purl":"pkg:composer/smarty/smarty","source":"GHSA-f6wf-28g6-769x"}],"prev":{"headline":"Froxlor: Credential and 2FA secret disclosure via Froxlor API endpoints","id":"CVE-2026-62988"},"products":["smarty"],"published":"2026-08-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-07","vendors":["smarty-php"]},"summary":"An attacker can use symbolic links to bypass directory restrictions and read arbitrary files accessible to the PHP process.","url":"https://insights.sbomify.com/CVE-2026-62992/"}