{"answers":{"affected":"2 open source packages ship an affected version, including smarty/smarty.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62996 exists.","fix":"Upgrade smarty/smarty to 5.8.4 or later.","what":"CVE-2026-62996 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-62996 and fix it if it is affected.\n\nWhat it is: CVE-2026-62996 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62996 exists.\n\nAffected packages and fixed versions:\n- smarty/smarty (Packagist): affected from 5.0.0; fixed in 5.8.4\n- smarty/smarty (Packagist): affected from 5.0.0; fixed in 5.8.4\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-62996/ (Markdown: https://insights.sbomify.com/CVE-2026-62996/index.md)","id":"CVE-2026-62996","markdown":"https://insights.sbomify.com/CVE-2026-62996/index.md","name":"CVE-2026-62996","record":{"aliases":["GHSA-rjhh-76wf-8xmw","UBUNTU-CVE-2026-62996"],"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 read arbitrary local files by exploiting insufficient stream wrapper restrictions in the Smarty PHP template engine.","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-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. From 5.0.0 until 5.8.4, Smarty's stream: resource-name handling does not adequately restrict which PHP stream wrappers and filter chains can be referenced from a template, allowing a php://filter-wrapped resource name to be used to read the contents of arbitrary local files accessible to the PHP process. An attacker able to author or influence a template's resource reference could exploit this to disclose sensitive file contents outside the intended template/config scope. This issue is fixed in version 5.8.4.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Smarty Security stream restriction bypass through stream: resource","id":"CVE-2026-62996","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"Kedro-Datasets: Remote code execution in experimental `PyTorchDataset` via unsafe `torch.load`","id":"CVE-2026-62997"},"packages":[{"ecosystem":"Packagist","fixed":["5.8.4"],"introduced":["5.0.0"],"last_affected":[],"package":"smarty/smarty","purl":null,"source":"GHSA-rjhh-76wf-8xmw"},{"ecosystem":"Packagist","fixed":["5.8.4"],"introduced":["5.0.0"],"last_affected":[],"package":"smarty/smarty","purl":"pkg:composer/smarty/smarty","source":"GHSA-rjhh-76wf-8xmw"}],"prev":{"headline":"joserfc accepts JWT with padding, leading to JWT malleability","id":"CVE-2026-62995"},"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-07","vendors":["smarty-php"]},"summary":"An attacker can read arbitrary local files by exploiting insufficient stream wrapper restrictions in the Smarty PHP template engine.","url":"https://insights.sbomify.com/CVE-2026-62996/"}